STATE-CURRENT: 2026-10-16 integration wave snapshot (five fixes landed, r161/r162 greens, dual-guest bring-up)

1 files changed, 25 insertions, 5 deletions

diff --git a/STATE-CURRENT.md b/STATE-CURRENT.md
index d26ffec..9bfbff5 100644
--- a/STATE-CURRENT.md
+++ b/STATE-CURRENT.md
@@ -1,8 +1,7 @@
 # Open-IOV Current State
 
-> **Snapshot: 2026-10-14 ~13:30 (physical/guest campaign data current to the
-> live r139 cycle at snapshot time; simulator workstream status 2026-10-03;
-> page reorganized and debugging-options catalogue added 2026-10-05).**
+> **Snapshot: 2026-10-16 ~15:30 (integration wave: bigpath+dual merged, five fixes
+> landed through `7d123630`; live r161/r162 cycles on kernel 6.8.0-147).**
 > This is a dated public
 > status page, not live state; it is refreshed on every progress check. Live
 > working notes are maintained outside this repository; the public
@@ -231,8 +230,29 @@ isolation, performance, portability).
       simultaneous guests; (c) `lottery` - analysis proving the completion ack is not
       an execution witness, rejecting naive fail-closed (idempotent-client false
       positives), and ranking the next experiments (win0 bank rotation, qmdwin
-      double-buffer, warm-sem retry, executed-vs-wedged discriminator). Host clean,
-      GPU green, VM left live; user-requested poweroff at pause.
+       double-buffer, warm-sem retry, executed-vs-wedged discriminator). Host clean,
+       GPU green, VM left live; user-requested poweroff at pause.
+      **Update 2026-10-16 ~15:30 (integration wave; five fixes landed; no reboots):**
+       bigpath + dual merged to master; then, pushed through `7d123630`: qmdwin
+       double-buffering (E3); a warm-sem-push discriminator on zero-write retries (E5 -
+       proved the engine is ALIVE during the acked-no-execute class, so it is a
+       launch-form/dispatch race, not an engine wedge); R1/m157-m159 - busy-refused GR
+       captures now wait (bounded) and retry inline, so multi-launch clients' kernels all
+       execute (streams2's three kernels ran serially on the physical engine); and a
+       guest-side demand-pin offset fix (CE-window mask `&0xFFFFF` folded every 1 MB rank
+       to page 0) that removed the repeat-client stall class. Verified live (r161/r162,
+       512M mdev): the exact user repro (`victory_mail` then `victory_matmul`) green
+       back-to-back with `bad=0` + `STATUS OK`, and a four-consecutive-client green boot
+       (`victory_mail` x2, `victory_matmul`, `smiley`). Remaining single-guest gaps: the
+       intermittent acked-no-execute launch lottery (one `smiley` pass in r162) and a
+       streams2 second-channel capture miss (entry consumed before its push page was
+       readable); both characterized with fix directions in the private handoff.
+       **1.0 multi-tenant:** two mdevs of different VRAM sizes (512M + 2 GiB) and two
+       QEMU guests coexist; guest B reports `memory.total = 2048 MiB` with `nvidia-smi`
+       green. Guest-B CUDA is blocked by the shared host pin table (cross-guest
+       contamination demonstrated live) and needs the per-guest ownership rework
+       (owner-tagged pin/map/pending lookups) before any dual-CUDA claim. No reboot;
+       host GPU green; both guests left running.
 - **Guest frontier: FIRST GREEN END-TO-END GUEST CUDA, NOW UNDER HARDENING
   (2026-10-04 ~16:20; hardening 2026-10-05 overnight).** The emulation-only
   ("no-claim") campaign runs an unmodified guest CUDA program to completion