diff options
Diffstat (limited to 'STATE-CURRENT.md')
| -rw-r--r-- | STATE-CURRENT.md | 8 |
1 files changed, 5 insertions, 3 deletions
diff --git a/STATE-CURRENT.md b/STATE-CURRENT.md index af7165d..a79d5f2 100644 --- a/STATE-CURRENT.md +++ b/STATE-CURRENT.md @@ -253,9 +253,9 @@ isolation, performance, portability). 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. - **Update 2026-10-16 ~22:35 (reliability wave 2, m163-m170; seven cycles, no host reboots):** + **Update 2026-10-16 ~22:35, extended ~23:05 (reliability wave 2, m163-m170; cycles r169-r177, no host reboots):** the stall classes that made clients freeze at DEVICE are largely closed. Fixed and - verified across boots r172/r174/r175: the session flush can no longer wipe a live + verified across boots r172/r174/r175/r177: the session flush can no longer wipe a live session (a deferred flush executed with the client's channels valid, dropped its queued launch release, and froze it in the tracker wait); GR entries whose decode sees QMD words but builds no launch candidate are held and re-captured instead of @@ -266,7 +266,9 @@ isolation, performance, portability). forwarding stale operands; device-destination copies answered only by a page-table walk wait (bounded 3 s) for a pin. `victory_mail`, `victory_matmul` and `smiley` are green on every boot of the wave, including the user's exact repro and mail as - the eighth client of a used boot. streams2/memset2d/saxpy no longer wedge - they + the eighth client of a used boot; r177 ran mail, matmul, smiley, matmul (repeat) + and mail GREEN back-to-back as its first five clients. streams2/memset2d/saxpy no + longer wedge - they now fail fast (~35-60 s) on the remaining data class: an H2D into a device buffer that does not land where the launch's data fill later reads the operand (the vidmem write path vs the fill's read path divergence; analysis and the ranked |