diff options
| author | Arthur Hanson Rasmusson <arthur@vgpu.io> | 2026-10-08 11:07:42 -0400 |
|---|---|---|
| committer | Arthur Hanson Rasmusson <arthur@vgpu.io> | 2026-10-08 11:07:42 -0400 |
| commit | 54bc80ae33addabc73a5bc1b0881423a63bc9862 (patch) | |
| tree | 8555a40907d666bb97925d3b78cd6f008c89bfd8 /tools/cuda-bridge/check_module_layout.py | |
| parent | 7ce387f3e3e5aac043b6d46a4451269c2b5c5233 (diff) | |
| download | open-iov-54bc80ae33addabc73a5bc1b0881423a63bc9862.tar.gz open-iov-54bc80ae33addabc73a5bc1b0881423a63bc9862.zip | |
vgsp-rm: PROMOTE_CTX reply must keep bInitialize set (ISSUE-0001)
kgrobjPromoteContext_IMPL marks each ctx buffer initialized when the
REPLY's promoteEntry[i].bInitialize is set:
if (!params.promoteEntry[i].bInitialize) continue;
kgrctxMarkCtxBufferInitialized(...);
The flag is the server's initialized-ACK, so the correct emulation reply is
a verbatim echo (the physical backend owns residency; the control answers
SUCCESS). 7ce387f3 cleared the flag believing the check inverted - that
skipped the mark and left the RM re-promoting the same buffers forever.
Restore echo semantics with the source-cited comment.
Diffstat (limited to 'tools/cuda-bridge/check_module_layout.py')
0 files changed, 0 insertions, 0 deletions