summaryrefslogtreecommitdiffstats
path: root/tools/rmq/kmod/wpr2_reset_kmod.c
diff options
context:
space:
mode:
authorArthur Hanson Rasmusson <arthur@vgpu.io>2026-10-22 16:00:07 -0400
committerArthur Hanson Rasmusson <arthur@vgpu.io>2026-10-22 16:00:07 -0400
commitfe2191aa24e766d6792964561868563690d36992 (patch)
tree4909629c2cdd5fbcc9fa7a95fb90faae8eba294d /tools/rmq/kmod/wpr2_reset_kmod.c
parentbdf1369d39d6767b4c857e7ddb8f8fdd87cb682e (diff)
downloadopen-iov-fe2191aa24e766d6792964561868563690d36992.tar.gz
open-iov-fe2191aa24e766d6792964561868563690d36992.zip
r489 the proper large-reply framing for GSP_RM_CONTROL: replies beyond the driver's pRpc->maxRpcSize (65080; pinned by the guest's own remainingSize 0x940 arithmetic for the 67448-byte PERF_VPSTATES_INFO reply) are now sent with the GSP continuation-record protocol - first frame length = maxRpcSize, then NV_VGPU_MSG_FUNCTION_CONTINUATION_RECORD frames of up to maxRpcSize-32 bytes each, exactly like the host GSP's _rpcWriteContinuationEntries. Replaces the r487 clamp (which produced a record the guest refused, and a size the guest then waited on fn-71 continuations for). Root: the GL VASpace construction and 3D engine selection die on this control's reply
Diffstat (limited to 'tools/rmq/kmod/wpr2_reset_kmod.c')
0 files changed, 0 insertions, 0 deletions