summaryrefslogtreecommitdiffstats
path: root/tools/cuda-ab/run/vector_add
diff options
context:
space:
mode:
authorArthur Hanson Rasmusson <arthur@vgpu.io>2026-10-22 04:25:41 -0400
committerArthur Hanson Rasmusson <arthur@vgpu.io>2026-10-22 04:25:41 -0400
commit5cdf11a092350c07e8df7549c766fadf7e75929a (patch)
treef6038291fc47f2ac8a0e35e2ac0568e2c303c98b /tools/cuda-ab/run/vector_add
parent19399f4f62a6adb282f8b4aa4cf174f42a05e404 (diff)
downloadopen-iov-5cdf11a092350c07e8df7549c766fadf7e75929a.tar.gz
open-iov-5cdf11a092350c07e8df7549c766fadf7e75929a.zip
r453 rel_mod=1 default: route the forwarded QMD release0 to the module semaphore so the guest-visible release word is authored by the host only on the completion edge (after the retire wait and after the bounce copy-out shipped the engine's stores). With the historical engine-authored guest release the guest's stream-ordered readback could be satisfied while the host copy-out was still pending, so streams2's c2 / memcpy_roundtrip's memset phase / streams_events' chain read pre-launch content. Evidence on r453 (with the r452 FNV change-detection fix): rel_mod=0 -> 11/15 battery; rel_mod=1 -> 13/15 (victory_streams_events and memcpy_roundtrip flip green), no stalls across the full battery, victory_mail + victory_saxpy clean. The r414 stall hole is closed by the r420b per-outcome authoring; rollback is one echo to 0
Diffstat (limited to 'tools/cuda-ab/run/vector_add')
0 files changed, 0 insertions, 0 deletions