summaryrefslogtreecommitdiffstats
path: root/wiki/open-iov.org/images/7
diff options
context:
space:
mode:
authorArthur Hanson Rasmusson <arthur@vgpu.io>2026-10-22 15:47:32 -0400
committerArthur Hanson Rasmusson <arthur@vgpu.io>2026-10-22 15:47:32 -0400
commit737aabc28bb4340e80cf801abf85cfc9e6443644 (patch)
treeb79567240a0c4992f8954a88770fb1d6588d50e1 /wiki/open-iov.org/images/7
parenta42fdb2cbe6a9b294a160860f38485ba1eb93c34 (diff)
downloadopen-iov-737aabc28bb4340e80cf801abf85cfc9e6443644.tar.gz
open-iov-737aabc28bb4340e80cf801abf85cfc9e6443644.zip
r487 THE GL/VULKAN VASPACE WALL: clamp RM_CONTROL replies to the 64 KB wire record bound (16 x 4096; guest GspMsgQueueReceiveStatus rejects hdr + rpc.length beyond it - 'Incorrect message length 67448', rpcRecvPoll 0x3a, NV_ERR_INVALID_PARAMETER). The stock driver sends PERF_VPSTATES_INFO (0x2080a0a4, paramsSize 67392) during Xorg VASpace construction; the generic reply echoed the whole buffer as a 17-element record the guest refused, vmmCreateVaspace returned ffff and GL died with 'Failed to allocate VASpace object' / EGL_BAD_ALLOC on every prior session. A real GSP-RM cannot reply past the bound either; the echo is clamped with the tail zeroed
Diffstat (limited to 'wiki/open-iov.org/images/7')
0 files changed, 0 insertions, 0 deletions