summaryrefslogtreecommitdiffstats
path: root/wiki/GSP-570.144W-Firmware-Analysis.md
diff options
context:
space:
mode:
authorArthur Hanson Rasmusson <arthur@vgpu.io>2026-10-07 13:22:11 -0400
committerArthur Hanson Rasmusson <arthur@vgpu.io>2026-10-07 13:22:11 -0400
commit359345cdda1d047fb1e2ba5259502ec47a7aac37 (patch)
tree22eed9da3ed4758bf4167a534670800936e33350 /wiki/GSP-570.144W-Firmware-Analysis.md
parentbcaab155a1318373b6c3a4c83fbfe2d0dbf1f44e (diff)
downloadopen-iov-359345cdda1d047fb1e2ba5259502ec47a7aac37.tar.gz
open-iov-359345cdda1d047fb1e2ba5259502ec47a7aac37.zip
vgsp: m93 - dump the launch-time instance SC/PDB words (w126..131, w166..173)
The m90/m91 decode pinned the SM I-fetch failure to WARP_ESR MMU_NACK at the window-0 shadow VA, while everything FE-side resolves the same small-PT line. The SC array (RAMIN words 166+: VALID mask, then per-VEID SC_PAGE_DIR_BASE LO/HI/flags) is the page directory the SMs' walk is expected to use; log it raw at launch time so the next cycle shows which base/target/flags the server actually programmed (and whether it is the module VASPDB root).
Diffstat (limited to 'wiki/GSP-570.144W-Firmware-Analysis.md')
0 files changed, 0 insertions, 0 deletions