summaryrefslogtreecommitdiffstats
path: root/debug/risc-v-gsp-rm-vm/docs/06-ACCURACY.md
diff options
context:
space:
mode:
Diffstat (limited to 'debug/risc-v-gsp-rm-vm/docs/06-ACCURACY.md')
-rw-r--r--debug/risc-v-gsp-rm-vm/docs/06-ACCURACY.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/debug/risc-v-gsp-rm-vm/docs/06-ACCURACY.md b/debug/risc-v-gsp-rm-vm/docs/06-ACCURACY.md
index e55162d..ebc9226 100644
--- a/debug/risc-v-gsp-rm-vm/docs/06-ACCURACY.md
+++ b/debug/risc-v-gsp-rm-vm/docs/06-ACCURACY.md
@@ -7,7 +7,7 @@
## 1. Purpose
risc-v-gsp-rm-debugger exists to measure how accurately Open-IOV's GSP emulation
-(`gsp-rm-vfio` and the in-kernel emulation) reproduces the behaviour of the
+(`vgsp` and the in-kernel emulation) reproduces the behaviour of the
real GSP firmware, and to make the firmware itself analysable. That makes
accuracy a first-class deliverable, not an assumption. This document defines
the fidelity levels, the measurement contract, and the rules for honest
@@ -73,7 +73,7 @@ Re-host fidelity must be stated per module in the session metadata, and every
"this is what the firmware does" claim should be cross-checked against the
physical RPC traces (PLAN B) before it is used to change the emulation.
-## 5. Measurement contract for `gsp-rm-vfio` accuracy
+## 5. Measurement contract for `vgsp` accuracy
Define these metrics once and use them everywhere: