diff options
| author | Arthur Hanson Rasmusson <arthur@vgpu.io> | 2026-10-23 12:24:19 -0400 |
|---|---|---|
| committer | Arthur Hanson Rasmusson <arthur@vgpu.io> | 2026-10-23 12:24:19 -0400 |
| commit | d45db82ea2656f536f08d4c80da406be81dea21f (patch) | |
| tree | 8275687beb77cb33241eefd57fbc5732ca838266 /DUAL-REPORT.md | |
| parent | ce499542ca2560a25ad1d94890838d741dba7238 (diff) | |
| download | open-iov-d45db82ea2656f536f08d4c80da406be81dea21f.tar.gz open-iov-d45db82ea2656f536f08d4c80da406be81dea21f.zip | |
vgsp-sema r549: cap the dead-operand walk at 3 s per entry (opdef hold + opfail window)
r548 evidence (matmul, reused channel handle 0x5c000059 after the previous
client exited): the new client's init sequence carries ~65 small
device-destination ops whose operands no resolver covers (memcopy/memset
rc=-2, SVC_VAS_FLOOR destinations like 0x2000c0100). Each one armed the
opdef hold, expired after exactly 10 s (OPDEF-EXPIRED idx 7..18 at ~10.5 s
spacing) and only then released the counter increment the client waits on:
the pump walked one entry per 10 s while the client spun at 100 % CPU
(12+ min, battery timeout).
The two bounds were both 10000 ms. Ops that DO resolve show 0.5-2 s pin
latency (SVC_OPDEF_HOLD_MS comment), so 3000 ms keeps the m163 guarantee
(a failed device copy still gets its retry once the pins land) and the
op-failure latch now fires on the first 3 s retry instead of a second
10 s window. Both are pure bounds - no path loses its retry.
Diffstat (limited to 'DUAL-REPORT.md')
0 files changed, 0 insertions, 0 deletions
