summaryrefslogtreecommitdiffstats
path: root/scripts/auto-opencode-setup.sh
diff options
context:
space:
mode:
authorArthur Hanson Rasmusson <arthur@vgpu.io>2026-09-28 09:09:13 -0400
committerArthur Hanson Rasmusson <arthur@vgpu.io>2026-09-28 09:09:13 -0400
commitbde9352a0f84bdf0ef7bdfdc150f5f11a9200af3 (patch)
tree8f151d950f65c00d191d7babbaad10e07b41f36a /scripts/auto-opencode-setup.sh
parent2133dd1fd82b4fd37df45e134b9a073f081d49d1 (diff)
downloadopen-iov-bde9352a0f84bdf0ef7bdfdc150f5f11a9200af3.tar.gz
open-iov-bde9352a0f84bdf0ef7bdfdc150f5f11a9200af3.zip
sem: run GR channels - accept CE methods on subchannel 0, discover GR rings
- The CE semaphore/memset method groups also arrive on subchannel 0 (CUDA's push library binds the copy class on compute channels to carry the work-submission releases), so the stream decoder accepts both 0 and 4. - GR (compute) channel rings live in the same video-memory allocation as the CE rings, 0x3000 bytes per channel after them: ring (0x2000) at ce_end + 0x3000*rank, USERD at +0x2000. Discover and pin them once the CE ranks are known; verified against ring entry 0 (1 MB aligned push VA in the client window, sane length) and the USERD's put/get, so a layout change costs a failed pin, not a wrong one. Gated by sema_gr_rings (default on). - memprobe: require the sem-VA triple in the sem-object scanner (a bare qword in the window matches thousands of unrelated pointers once the ring/pushbuffer windows are part of the range). Live evidence: ring entries read through the guest's /proc/pid/mem decode to the GR channels' first pushes; pinning the ring (fb 0x140000+0x3000*rank), USERD (ring+0x2000) and first-push pages made all 20 GR channels execute their entry 0 for the first time (get=1 sub=1).
Diffstat (limited to 'scripts/auto-opencode-setup.sh')
0 files changed, 0 insertions, 0 deletions