diff options
| author | Arthur Hanson Rasmusson <arthur@vgpu.io> | 2026-10-05 12:50:44 -0400 |
|---|---|---|
| committer | Arthur Hanson Rasmusson <arthur@vgpu.io> | 2026-10-05 12:50:44 -0400 |
| commit | 5f511b70d272a898d0dc5a46d56ccb07c69060f0 (patch) | |
| tree | 10a2c58c4c50c7db44193d734f00bd97487eabc0 /debug/risc-v-gsp-rm-vm/tests/test_device_map.py | |
| parent | 79327c204237052d16b948c8fb42e0d4c992564e (diff) | |
| download | open-iov-5f511b70d272a898d0dc5a46d56ccb07c69060f0.tar.gz open-iov-5f511b70d272a898d0dc5a46d56ccb07c69060f0.zip | |
vgsp: GR ctx query ABI fix, server-managed ctx map exclusion, raw diag capture
- NV2080_CTRL_GR_CTX_BUFFER_INFO is 80 bytes (NvBool is NvU8: flags at
56..59, uuid at 60) and the params are 5136 bytes, not 5648; the previous
ABI mismatch is why GR_GET_CTX_BUFFER_INFO returned NV_ERR_INVALID_ARGUMENT
(0x1f) on every shared-VAS cycle.
- Under gsp_phys_srv_ctxbuf the GSP-RM server allocates/maps/commits the
engine context itself: do not install the client GR context-window PDEs and
do not map the client ctx VA in the PDB, so a client mapping cannot clobber
the server's own context-window page table.
- Dump the server-written INSTANCE/RAMFC chunks after BIND/SCHEDULE on the
shared GR path so the committed engine-context pointer/VA can be located.
- Emit the full NOCAT diag buffer as 16-byte hex rows (the printable copy is
capped at 192 dotted bytes and hides binary fault dumps).
Untested on hardware at commit time; the next supervised GR cycle validates.
Diffstat (limited to 'debug/risc-v-gsp-rm-vm/tests/test_device_map.py')
0 files changed, 0 insertions, 0 deletions
