diff options
Diffstat (limited to 'debug/risc-v-gsp-rm-vm/RISC-V-GSP-RM-DEBUGGER-ROADMAP.md')
| -rw-r--r-- | debug/risc-v-gsp-rm-vm/RISC-V-GSP-RM-DEBUGGER-ROADMAP.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/debug/risc-v-gsp-rm-vm/RISC-V-GSP-RM-DEBUGGER-ROADMAP.md b/debug/risc-v-gsp-rm-vm/RISC-V-GSP-RM-DEBUGGER-ROADMAP.md index 88183ea..a7a8227 100644 --- a/debug/risc-v-gsp-rm-vm/RISC-V-GSP-RM-DEBUGGER-ROADMAP.md +++ b/debug/risc-v-gsp-rm-vm/RISC-V-GSP-RM-DEBUGGER-ROADMAP.md @@ -12,7 +12,7 @@ Open-IOV's hardest long-term problem is not writing the emulation once — it is **surviving adversarial firmware change**. NVIDIA ships new GSP images, new device pairings and new architectures on independent schedules, and the firmware is deliberately opaque (stripped, signed, hardware-coupled, with -non-recoverable boot states). To keep `open-iov-vfio` accurate across that +non-recoverable boot states). To keep `vgsp` accurate across that churn, the project needs a toolchain that can: 1. **Run** firmware off-hardware, safely and repeatably. @@ -22,7 +22,7 @@ churn, the project needs a toolchain that can: 4. **Compare** — hardware vs VFIO vs simulation, old vs new firmware, with a metric contract instead of anecdotes. 5. **Reimplement** — turn observed behaviour into reviewed code in - `open-iov-vfio` with evidence attached. + `vgsp` with evidence attached. risc-v-gsp-rm-debugger is the vehicle for that program. It is explicitly a **development environment**, never a shipped component. @@ -226,7 +226,7 @@ reimplement quickly. Observe what each service reads/writes (watchpoints, TCG trace) and infer capabilities (which objects, ranges, controls it touches); compare with the declared/emulated capability model; surface least-privilege and security -findings for `open-iov-vfio`. +findings for `vgsp`. ### H4.3 Mutation and fuzzing Feed malformed construction/control traffic into re-hosted or simulated @@ -247,7 +247,7 @@ The canonical loop for any behaviour: 1. Observe on hardware/VFIO (reference capture). 2. Observe in risc-v-gsp-rm-debugger (simulator, replayable). 3. `compare` + metric table M1–M6 (docs/06-ACCURACY.md). -4. Implement in `open-iov-vfio` with the session directories attached as +4. Implement in `vgsp` with the session directories attached as evidence. 5. Re-run the same stimulus; the metric table must improve or stay equal. This loop becomes a scripted harness ("consensus harness") so every change |