summaryrefslogtreecommitdiffstats
path: root/STATE-CURRENT.md
diff options
context:
space:
mode:
authorArthur Hanson Rasmusson <arthur@vgpu.io>2026-10-06 23:50:00 -0400
committerArthur Hanson Rasmusson <arthur@vgpu.io>2026-10-06 23:50:00 -0400
commit374292ae2d6379ffab6ed5b7eeedf712581365ab (patch)
tree49a5b7a934d7c559219d56a036fc6f1ae7b43f19 /STATE-CURRENT.md
parent8948759ebdfd1372829222c03c90edfa44d93d72 (diff)
downloadopen-iov-374292ae2d6379ffab6ed5b7eeedf712581365ab.tar.gz
open-iov-374292ae2d6379ffab6ed5b7eeedf712581365ab.zip
vgsp: m69 - window-0 shadow pool for the QMD program/param pages
m68 proved the program page's shadow copy contains real SASS (SASS_version 0x75) and the prefetch pair is fixed, yet the engine still never completes and never writes its release anywhere - including a window-0 module sem. Best remaining suspect: the window-1 scratch VA range (PT chain installed by DMA_UPDATE_PDE_2 pdeIndex=1) has never been proven readable by the GR engine core, unlike the window-0 GPFIFO/PB/QMDWIN small-PT line. m69 plants 8 module pages at VAs 0x108000..0x10f000 (slots 0x108..0x10f, same 128 B PT fetch line, planted before first fetch like qmdwin), copies the resolved program/param page content into them at launch and rewrites the QMD pointer pairs there (param=32, program=48). Param: gsp_phys_rmcall_gr_shadow_win0.
Diffstat (limited to 'STATE-CURRENT.md')
0 files changed, 0 insertions, 0 deletions