Skip to main content

S0: Follow one I/O

Question: Where do payload and modeled time travel?

Time: 30 minutes. Prerequisites: completed setup. See qualification and limitations before running.

Mechanism​

A BlackBox write separates payload copying from modeled NAND scheduling
The FEMU Manual traces payload movement and modeled completion time separately.
  1. Application issues a read or write.
  2. FEMU dispatches the command and models the device.
  3. The guest compares returned data with its original input.

Predict​

Does a successful command prove the bytes are correct?

Write down a predicted state or counter change before executing the commands.

Run​

Host terminal, unless a command is explicitly labelled Guest. Source and export the identity fields from connection.env. These labs overwrite the explicit disposable namespace. Use a fresh VM for each independent arm.

bash labs/bin/preflight.sh labs/guest/lab-s0.sh /dev/nvme0n1

Check your evidence​

  • Exactly 1 MiB written at the specified offset reads back unchanged.
  • Identify information, versions and raw counters are preserved.

The host runner retrieves raw receipts and preserves the guest exit status. Keep unsuccessful attempts; do not replace them with a later successful log.

Interpret​

Which parts of the path disappear when replacing BBSSD with NoSSD?

Explain the mechanism and the measurement boundary. A throughput number by itself is not evidence that the intended feature was exercised.

Recover​

  • Wrong serial or capacity: stop and inspect the launch receipt.
  • Zero NAND counters in NoSSD are expected; they do not indicate a failed readback.

Save the receipt before resetting the VM.

Materials and source​

Slides, scripts and worksheet. Videos are not yet recorded. The frozen public source is 1918eb9795ba. The FEMU Manual explains the implementation and supported properties.