summaryrefslogtreecommitdiffstats
path: root/kernel/gsp_cuda_bridge.c
diff options
context:
space:
mode:
authorArthur Hanson Rasmusson <arthur@vgpu.io>2026-11-15 15:15:14 -0500
committerArthur Hanson Rasmusson <arthur@vgpu.io>2026-11-15 15:15:14 -0500
commitc9661edb46f087c67ffd9dca7ac30b291503ecd3 (patch)
treed5d8d7ca00d013a570b6f97e8334e78ed90475af /kernel/gsp_cuda_bridge.c
parent190d2bc7b41557c7caa5ea4fede48d15e6d7491e (diff)
downloadopen-iov-c9661edb46f087c67ffd9dca7ac30b291503ecd3.tar.gz
open-iov-c9661edb46f087c67ffd9dca7ac30b291503ecd3.zip
vgsp: eng59b - do not let the arming launch consume the release carrier; re-arm in the pump
The saved-window release carrier was armed inside the pack-completing launch's own build, and the client-first cancel treated that same launch (and its retries) as the next client launch, silently dropping the claim. c762: MME-CARRY-SAVE (win=240 held=68) -> MME-CARRY-ARM mode=release -> the arming launch ran mac=0 (LOAD-ONLY, window dropped, held CALLs still owed) -> no FIRE, no synthetic push, no mac=0x22. Track the arming launch identity (h + push) and keep the claim armed across it; only the MME-PACK-REARM edge (calls actually released), a real consumer, context/handle changes, or a launch error cancels/consumes. Add a pump-side re-arm once pack_done_gen is set, and bounded MME-CARRY-HOLD receipts for every skip. One fire per pack completion, no retries. Build rc 0; validation pending (c762-class boot with sema_gl_mme_pack_release=1).
Diffstat (limited to 'kernel/gsp_cuda_bridge.c')
0 files changed, 0 insertions, 0 deletions