summaryrefslogtreecommitdiffstats
path: root/scripts
diff options
context:
space:
mode:
authorArthur Hanson Rasmusson <arthur@vgpu.io>2026-09-21 19:04:05 -0400
committerArthur Hanson Rasmusson <arthur@vgpu.io>2026-09-21 19:04:05 -0400
commit6b686f70d8ff3e6340e8307c95847cd1eed4f2ae (patch)
tree71cf22aff298900e4073427534eab4ce93a6ef84 /scripts
parent256c5308423befddc20bdf7e59a663f3f1b683ae (diff)
downloadopen-iov-6b686f70d8ff3e6340e8307c95847cd1eed4f2ae.tar.gz
open-iov-6b686f70d8ff3e6340e8307c95847cd1eed4f2ae.zip
kernel: Fix FIFO table fortify_panic + GSP boot-state reset on queue death + ISO fbRegion
- gsp_rm_handle_fifo_device_table: read baseIndex from the queue element buffer (req_data + hdr), not past the local 24-byte header struct - FORTIFY proved the old memcpy always overflows -> fortify_panic killed gsp_emu_0 mid RmInitNvDevice (guest timed out on fn 76). - gsp_emu_clear_boot_state: clear WPR2/RISCV/mailboxes/stage tracker and reset GSP-RM queue state. Turing guests produce no observable BAR0 writes on unload, so the next probe's _kgspBootGspRm failed with 'unexpected WPR2 already up'. Trigger on ENGINE reset and on detected queue death (insane writePtr jump / garbage element signature). - GspStaticConfigInfo fbRegion[0].supportISO=1: memmgrCalcReservedFbSpace asserts some region supports ISO 'even with no display'; without it kdispStateInitLocked couldn't allocate clientChannelTable. - .gitignore: scripts/git-push-vgpu.sh (local per-machine helper)
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions