docs(qemu): clarify post_exec runs after harness completion #3671
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR clarifies the execution timing of
EmulatorHooks::post_exec, documentingthat it runs after the harness completes and after snapshot restoration.
It also adds a small lifecycle note in the qemu_baremetal low-level example to
make it explicit that
qemu().run()completes the full harness execution cycle.This resolves the confusion described in #2765 regarding guest memory reads in
post_exec.Checklist
./scripts/precommit.shand addressed all comments