From 1c99bfbeffff04529f6f669601fdf835a73778da Mon Sep 17 00:00:00 2001 From: Arthur Hanson Rasmusson Date: Fri, 2 Oct 2026 11:44:31 -0400 Subject: rename (cosmetic): green-eye -> risc-v-gsp-rm-debugger in user-facing names, docs, CLI, launcher and CI workflow; internal greeneye package/module identifiers unchanged (includes in-flight greeneye module edits present in the tree) --- debug/risc-v-gsp-rm-vm/docs/07-PORTABILITY-PLAYBOOKS.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) (limited to 'debug/risc-v-gsp-rm-vm/docs/07-PORTABILITY-PLAYBOOKS.md') diff --git a/debug/risc-v-gsp-rm-vm/docs/07-PORTABILITY-PLAYBOOKS.md b/debug/risc-v-gsp-rm-vm/docs/07-PORTABILITY-PLAYBOOKS.md index 5426bf1..b0c8c3f 100644 --- a/debug/risc-v-gsp-rm-vm/docs/07-PORTABILITY-PLAYBOOKS.md +++ b/debug/risc-v-gsp-rm-vm/docs/07-PORTABILITY-PLAYBOOKS.md @@ -5,7 +5,7 @@ These playbooks cover the three churn axes the project expects: a new GSP firmware version, the same firmware on a new device, and a new GPU architecture (e.g. GB10 / DGX Spark / Surface-class). They reuse the -project's existing version discipline and add green-eye's runtime layer. +project's existing version discipline and add risc-v-gsp-rm-debugger's runtime layer. ## 0. Common setup @@ -16,7 +16,7 @@ project's existing version discipline and add green-eye's runtime layer. 3. Build a symbol DB for the new image: * import the fwimage into the existing Ghidra project tooling (`tools/ghidra/analyze_fwimage.py`, `DecompileFunctions.java`), - * `./greeneye.sh symbols export --index -o symbols-.json`. + * `./risc-v-gsp-rm-debugger.sh symbols export --index -o symbols-.json`. 4. Record a baseline session of the previous version (see P1.4) so the comparison has an anchor. @@ -29,7 +29,7 @@ emulation is adjusted. fwimage, diff the RPC dispatcher, subcommands, message layouts and version strings against the previous version (`cudatool.py delta`-style discipline for firmware; `diff_corpus.py` for the corpus). -2. **Probe the new image** — `./greeneye.sh probe `: record the +2. **Probe the new image** — `./risc-v-gsp-rm-debugger.sh probe `: record the first divergence and the first MMIO/read/write addresses. Compare with the previous version's probe; changed first-touch addresses are early structure-change signals. @@ -40,7 +40,7 @@ emulation is adjusted. * `greeneye record --kernel --duration N --snapshot ` or the scripted harness (`run`), * the real-backend reference traces for the same workload. -5. **Compare** — `./greeneye.sh compare dumps/ dumps/ --symbols`: +5. **Compare** — `./risc-v-gsp-rm-debugger.sh compare dumps/ dumps/ --symbols`: hit-count deltas per function, watchpoint deltas, written-page deltas. Investigate every function whose call-count changed before touching the emulation. @@ -60,7 +60,7 @@ emulation is adjusted. 2. Verify the firmware pairing: the image family (TU10x/GH100/LS10 …), FMC partition manifests, and the version string; a mismatched pairing presents as an emulation bug (the project learned this with 570.144 vs 570.211). -3. `./greeneye.sh probe ` on the new device image; compare +3. `./risc-v-gsp-rm-debugger.sh probe ` on the new device image; compare first-divergence maps with the reference device. Differences here usually point at profile data, not logic. 4. Re-run the P1.4/1.5 loop with the device profile applied; record probe + @@ -77,7 +77,7 @@ newer PMU/SEC2 images and possibly RV64GC rather than RV64IMAC). 1. **Confirm the ISA and image shape** — `file`/`readelf` the new fwimage: ISA string, segments, entry, compressed/float extensions. Update the rehost build flags (`-march=…`) accordingly; note that QEMU supports - RV64GC even if green-eye's demo uses IMAC. + RV64GC even if risc-v-gsp-rm-debugger's demo uses IMAC. 2. **Check the platform's boot variant** — newer platforms use FMC/manifest partition models (`uproc/*_riscv/fmc`, `safety/PMU-*`, `conf_compute` Init→ACR→RM flow). Record which partition model the image uses; the @@ -89,7 +89,7 @@ newer PMU/SEC2 images and possibly RV64GC rather than RV64IMAC). 4. **Run the P1 loop** with the new architecture profile; expect the probe to show *different* first-touch addresses (new register windows). Update the device-model scope in `08-ROADMAP.md` with what the probe revealed. -5. **Host portability** — green-eye itself is Python and QEMU; on aarch64 +5. **Host portability** — risc-v-gsp-rm-debugger itself is Python and QEMU; on aarch64 hosts install `qemu-system-misc` there and the same commands run. Keep host-specific paths out of session metadata. @@ -104,7 +104,7 @@ real firmware for a chosen workload. * or the vfio-mdev path with the same workload. Save the reference event stream in a session-compatible form (or the vendor logs plus a conversion note). -2. **green-eye capture:** run the same workload's firmware-side stimulus in +2. **risc-v-gsp-rm-debugger capture:** run the same workload's firmware-side stimulus in the rehosted simulator; record hooks, watchpoints, snapshots. 3. **Compare:** `greeneye compare` for hit/watch/write profiles; for RPC payloads use M2 field agreement and M3 ordering (a small script or a -- cgit v1.2.3