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.md8
1 files changed, 5 insertions, 3 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 a9a91aa..1a85ec5 100644
--- a/debug/risc-v-gsp-rm-vm/docs/06-ACCURACY.md
+++ b/debug/risc-v-gsp-rm-vm/docs/06-ACCURACY.md
@@ -124,9 +124,11 @@ Before trusting a risc-v-gsp-rm-debugger session:
## 8. Known accuracy gaps (living list)
1. Partial TU104 device model (S1, docs/36): the real 570.144 image is now
- served past the first unmapped access to B2 (relocation copy, 0 unknown
- MMIO) with a recorded boot shim; B3/B4 (CSB poll, message loop) are not
- reached, and the model is uncalibrated and partial.
+ served past the first unmapped access to B3 (libos init complete; the
+ message-loop task blocks in the port wait, 0 unknown MMIO) with the XMPU
+ model, a recorded boot shim and the libos service model; B4/B5
+ (host-traffic-triggered CSB poll, scripted message) are not reached, and
+ the model is uncalibrated and partial.
2. No time/concurrency model; multi-core and partition-switch behaviour is
approximated. Cycles are modeled defaults, not measured (docs/32).
3. PMU/SEC2/ACR/Booter behaviour is message-level only.