summaryrefslogtreecommitdiffstats
path: root/debug/risc-v-gsp-rm-vm/harness/value_demos/README.md
diff options
context:
space:
mode:
Diffstat (limited to 'debug/risc-v-gsp-rm-vm/harness/value_demos/README.md')
-rw-r--r--debug/risc-v-gsp-rm-vm/harness/value_demos/README.md10
1 files changed, 5 insertions, 5 deletions
diff --git a/debug/risc-v-gsp-rm-vm/harness/value_demos/README.md b/debug/risc-v-gsp-rm-vm/harness/value_demos/README.md
index e1a450c..96ce4d9 100644
--- a/debug/risc-v-gsp-rm-vm/harness/value_demos/README.md
+++ b/debug/risc-v-gsp-rm-vm/harness/value_demos/README.md
@@ -1,19 +1,19 @@
-# green-eye value-validation demos
+# risc-v-gsp-rm-debugger value-validation demos
-Runnable demonstrations that tie green-eye tool capabilities to **real**
+Runnable demonstrations that tie risc-v-gsp-rm-debugger tool capabilities to **real**
Open-IOV scenarios (cited from `Handoff-vGPU-IO.md` and the project docs) and
measure the time-to-value against the static/Ghidra-only baseline.
Each demo:
* names the real scenario (handoff PART/addendum + date) and what it cost;
-* prints the question, the green-eye commands used, the answer, the evidence
+* prints the question, the risc-v-gsp-rm-debugger commands used, the answer, the evidence
artifact and the elapsed wall-clock;
* writes a machine-readable `result.json` under `artifacts/<demo>/`;
* labels what is **measured on the analog** vs **projected for the real
case**; device-model-blocked scenarios say so explicitly.
-> green-eye is development-only tooling (docs/00); these demos never touch
+> risc-v-gsp-rm-debugger is development-only tooling (docs/00); these demos never touch
> hardware, a guest or a kernel module. The real `.fwimage` cannot boot
> without the H2 device model (docs/06 §3), so every demo is honest about
> being a *shape* reproduction on the bundled `uproc_demo` firmware + native
@@ -58,7 +58,7 @@ per-demo timeout and the full suite runs in ~18 s on the reference host
| s09 | `s09_grabbing_a_ghidra_address.py` | static/dynamic join; GPFIFO GET fault `0x40000` vs `0x101000` (PART 91 ADDENDUM 9 cycle 24) | hypothesis unproven until the decoded status-queue fault (8 cycles) | Ghidra addr + bias = runtime; hook hit + `greeneye_hits.tsv` (0.72 s) |
| s10 | `s10_full_session_evidence.py` | evidence pack for a milestone (docs/14 §6; cycles 11–13, 2026-10-01) | hashes/sessions/logs/compare gathered by hand per cycle | one run → analyze + compare + hits + manifest + M1–M6 (4.92 s) |
-Times are the measured green-eye path on the reference host (native for
+Times are the measured risc-v-gsp-rm-debugger path on the reference host (native for
s01–s08, QEMU for s09/s10); see `artifacts/results.json` for a fresh run.
## Projected vs measured