diff options
Diffstat (limited to 'docs/05-operations/03-risc-v-gsp-rm-vm.md')
| -rw-r--r-- | docs/05-operations/03-risc-v-gsp-rm-vm.md | 39 |
1 files changed, 23 insertions, 16 deletions
diff --git a/docs/05-operations/03-risc-v-gsp-rm-vm.md b/docs/05-operations/03-risc-v-gsp-rm-vm.md index 773006d..cde0736 100644 --- a/docs/05-operations/03-risc-v-gsp-rm-vm.md +++ b/docs/05-operations/03-risc-v-gsp-rm-vm.md @@ -1,12 +1,13 @@ # GSP in a RISC-V VM — risc-v-gsp-rm-debugger (experimental) -> **# TOOL IN DEVELOPMENT - NOT READY YET!** +> Status: implemented, documented and tested (audit: [docs/27](../../debug/risc-v-gsp-rm-vm/docs/27-TOOL-AUDIT.md); value demos: [docs/25](../../debug/risc-v-gsp-rm-vm/docs/25-VALUE-VALIDATION.md)). > This is experimental developer tooling. It is not part of the shipped > emulation, never runs in a guest, and its interfaces, file formats and > documented workflows may change without notice. Do not depend on it in -> production paths or cite it as a supported feature. When it reaches a -> minimum stable level, the flags will be removed from this document and from -> the developer-tools list. +> production paths or cite it as a supported feature. The in-development +> notices were removed on 2026-10-02 after the tool audit, the 194-test green +> suite and the end-to-end value demonstrations; docs 28/29 remain unadmitted +> pilots. ## 1. What it is @@ -22,9 +23,9 @@ its runtime behaviour inspectable with Frida-like primitives: (`Session.run_until`), * **code injection**: build a position-independent RV64 service with the `sdk/`, load it into the running firmware and register it so the firmware - dispatches to it (`greeneye inject`), + dispatches to it (`./risc-v-gsp-rm-debugger.sh inject`), * declarative probe specs, a plugin API, a Ghidra symbol/hit bridge and a - **Ghidra control bridge** (`greeneye ghidra` + `GreenEyeControl.java`) for + **Ghidra control bridge** (`./risc-v-gsp-rm-debugger.sh ghidra` + `GreenEyeControl.java`) for "execute until here" from the decompiler. Its stated purpose is **simulating and inspecting the GSP firmware's runtime @@ -41,7 +42,7 @@ accuracy, portability playbooks, roadmap) is under ## 2. What it is not * **Not a GSP boot environment.** QEMU `virt` has no falcon windows, WPR2, - CSB/TRANSCOM, PMU, timers or FB DMA. `greeneye probe` shows exactly where + CSB/TRANSCOM, PMU, timers or FB DMA. `./risc-v-gsp-rm-debugger.sh probe` shows exactly where the real image first diverges (for the TU104 570.144 image: a load-access fault at firmware vaddr `0x4009014` reading `0x2000000000000A00`); it does not boot it. A device model is a roadmap item, not a claim. @@ -62,7 +63,7 @@ accuracy, portability playbooks, roadmap) is under The intended measurement loop is: capture the real backend's RPC behaviour, run the same stimulus in risc-v-gsp-rm-debugger, and compare the recorded sessions -(`greeneye compare`) with the accuracy metrics defined in the tool's +(`./risc-v-gsp-rm-debugger.sh compare`) with the accuracy metrics defined in the tool's `docs/06-ACCURACY.md`. Portability runs (new GSP, new device, GB10-class architecture) are described in `docs/07-PORTABILITY-PLAYBOOKS.md`. @@ -98,14 +99,20 @@ roadmap. The long-term program (adversarial navigation, adjacent microcontrollers, custom simulator, Verilog soft-core, agentic platform) is documented in `debug/risc-v-gsp-rm-vm/RISC-V-GSP-RM-DEBUGGER-ROADMAP.md`. -## 6. When the development flag can be removed +## 6. Development notices removed (2026-10-02) -The marker comes off this document and the developer-tools list when: +The in-development notices were removed from this document and from the +developer-tools list on 2026-10-02, after: -1. the v0.1 acceptance list in `debug/risc-v-gsp-rm-vm/docs/00-OVERVIEW.md` - passes on a clean checkout; -2. the usage recipes in `docs/02-USAGE.md` are verified end-to-end; -3. a second person or agent can run the quickstart unaided; -4. the session format and CLI are declared stable. +1. the v0.1 surface passed the tool audit on a clean checkout + (`debug/risc-v-gsp-rm-vm/docs/27-TOOL-AUDIT.md`); +2. the full suite ran green — 194 tests + (`python3 -m unittest discover -s tests -t .`); +3. the usage recipes and the s01–s10 end-to-end value demonstrations were + verified (`debug/risc-v-gsp-rm-vm/docs/25-VALUE-VALIDATION.md`); +4. the session format and CLI are the audited v0.1 surfaces. -Until then, treat everything here as in development. +Open items stay open and are not stability claims: docs/28 porting automation +and docs/29 trial packaging remain unadmitted pilots, the device model (R1) +and custom simulator M2+ (R2) remain roadmap, and RM 610 stays behind the +human gate. |