summaryrefslogtreecommitdiffstats
path: root/debug/risc-v-gsp-rm-vm/tests/test_rm_capture.py
diff options
context:
space:
mode:
authorArthur Hanson Rasmusson <arthur@vgpu.io>2026-10-23 17:09:34 -0400
committerArthur Hanson Rasmusson <arthur@vgpu.io>2026-10-23 17:09:34 -0400
commit50adacc676f12e495acfb3ab5fbf7cce3baa7430 (patch)
tree65913d374451c88f458c1d62411d31de23c017fc /debug/risc-v-gsp-rm-vm/tests/test_rm_capture.py
parent0f73f4e69344eab4ffebaf310ba2d937b4471ea9 (diff)
downloadopen-iov-50adacc676f12e495acfb3ab5fbf7cce3baa7430.tar.gz
open-iov-50adacc676f12e495acfb3ab5fbf7cce3baa7430.zip
vgsp-gr r564: refuse a degenerate launch data set before the engine sees it
r565 evidence: the fill dropped 4 argument bases (GRFILL-DROP), RDW showed nrecs=2 where healthy launches run 968-969, the launch was still submitted and the backend timed out after ~19 s (GR forward failed rc=-110); the tail then authored the software release and the client kept spinning on a completion for a kernel that never ran - 20 s of backend occupancy plus a false completion, and a plausible wedge source for the following clients. gsp_phys_gr_submit now refuses n_data < GSP_PHYS_GR_MIN_DATA_RECS (16) with a loud line, failing fast into the same software-completion fallback without touching the engine.
Diffstat (limited to 'debug/risc-v-gsp-rm-vm/tests/test_rm_capture.py')
0 files changed, 0 insertions, 0 deletions