summaryrefslogtreecommitdiffstats
path: root/tools/cuda-ab/p2/expected
diff options
context:
space:
mode:
authorArthur Hanson Rasmusson <arthur@vgpu.io>2026-10-23 22:25:03 -0400
committerArthur Hanson Rasmusson <arthur@vgpu.io>2026-10-23 22:25:03 -0400
commit1c147816c12d1ca85fd5092d417d503eb86c6476 (patch)
tree0d414593c6815ca007040ddc0d99c2f0eb79865e /tools/cuda-ab/p2/expected
parent7eb410a59fa94e69cd6332ed8bf862d58e7d0cee (diff)
downloadopen-iov-1c147816c12d1ca85fd5092d417d503eb86c6476.tar.gz
open-iov-1c147816c12d1ca85fd5092d417d503eb86c6476.zip
vgsp-gr r585: demand the fill's dropped pages through the pin channel (the staging-pin coverage class)
The r584 boot's matmul draw: GR-DEC push=0x20043be64 n_data=2 dropped=18 partial=1 stalled=1 -> the r543 argument defer expired -> r564 degenerate refusal -> SW completion -> MATMUL bad=65536 csum=0. The dropped pages (the client's staging buffers 0x71b662c00000/c40000/c80000, 0x7dd0cac00000, kind=a) had NO injected mapping: the host pin stream's demand loop only parses "stalled VA #N: 0x..." lines, and the GRFILL-DROP line format is invisible to it - so the fill's retries never saw pins and the launch was SW-completed without running. r585: svc_log_stalled_va() for each dropped page (up to the 4 detailed per episode; the helper dedups per boot and the episode marker bounds the rate). The host demand loop (<=3 s) then pushes the VA to the guest scanner, whose pin lands inside the launch's bounded defer window on the retry - the demand path that already heals every other unresolved-VA class, now connected to the fill drops.
Diffstat (limited to 'tools/cuda-ab/p2/expected')
0 files changed, 0 insertions, 0 deletions