summaryrefslogtreecommitdiffstats
path: root/debug/risc-v-gsp-rm-vm/docs/29-PACKAGING-AND-TRIALING.md
diff options
context:
space:
mode:
authorArthur Hanson Rasmusson <arthur@vgpu.io>2026-10-02 11:44:31 -0400
committerArthur Hanson Rasmusson <arthur@vgpu.io>2026-10-02 11:44:31 -0400
commit1c99bfbeffff04529f6f669601fdf835a73778da (patch)
tree5867bab46e5848541df36c703f6fd8d6d0256e54 /debug/risc-v-gsp-rm-vm/docs/29-PACKAGING-AND-TRIALING.md
parent2fd653044127a665e4677a2cdfb58120d7b3e16b (diff)
downloadopen-iov-1c99bfbeffff04529f6f669601fdf835a73778da.tar.gz
open-iov-1c99bfbeffff04529f6f669601fdf835a73778da.zip
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)
Diffstat (limited to 'debug/risc-v-gsp-rm-vm/docs/29-PACKAGING-AND-TRIALING.md')
-rw-r--r--debug/risc-v-gsp-rm-vm/docs/29-PACKAGING-AND-TRIALING.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/debug/risc-v-gsp-rm-vm/docs/29-PACKAGING-AND-TRIALING.md b/debug/risc-v-gsp-rm-vm/docs/29-PACKAGING-AND-TRIALING.md
index 8be3704..c87806b 100644
--- a/debug/risc-v-gsp-rm-vm/docs/29-PACKAGING-AND-TRIALING.md
+++ b/debug/risc-v-gsp-rm-vm/docs/29-PACKAGING-AND-TRIALING.md
@@ -8,7 +8,7 @@
## 1. Purpose
-green-eye can already load an injected service into the native simulator and
+risc-v-gsp-rm-debugger can already load an injected service into the native simulator and
invoke it (docs/12, docs/16 ยง1.1, `harness/value_demos/s06_inject_service.py`).
That evidence lives in the tool tree: a reviewer needs the checkout, the built
demo and SDK, and the exact command sequence. `harness/package_sim.py` turns
@@ -111,7 +111,7 @@ not overwrite.
1. Receive `<package>.tar.gz` plus its sha256 out of band; verify
`sha256sum <package>.tar.gz`.
2. Extract and run: `./run.sh` (add `--budget N` for image packages). The
- script finds the green-eye tree by walking up, or via
+ script finds the risc-v-gsp-rm-debugger tree by walking up, or via
`GREENEYE_HOME=/path/to/risc-v-gsp-rm-vm`. Exit codes: `0` pass (or the
documented blocked image status), `1` assertion failure, `3` tree not found.
3. Read `results/results.md` first, then `results/results.json` for machines.
@@ -119,7 +119,7 @@ not overwrite.
flake: `assertions.failed` names the check (`handlers_slot_registered`,
`remote_ping`, `routes_agree`, `dispatch_hook_hits`, `uart_banner`, ...).
4. For deeper review, point the tools at `results/session/`:
- `./greeneye.sh analyze <pkg>/results/session` and
+ `./risc-v-gsp-rm-debugger.sh analyze <pkg>/results/session` and
`python3 -m greeneye compare baseline/results/session candidate/results/session`.
5. Verify provenance: each `components[].sha256` must match the packaged file;
`target.sha256`/`service.sha256` identify the inputs.