Open-IOV vGPU-IO: host-side GSP emulation for unmodified NVIDIA guest drivers https://git.vgpu.io/open-iov.git/atom?h=lottery 2026-10-08T18:10:23+00:00 2026-10-08T18:10:23+00:00 Arthur Hanson Rasmusson arthur@vgpu.io 2026-10-08T18:10:23+00:00 urn:sha1:94352c708442be843950e17e3613dce539ca9fdb The GMMU doc cited pre-a9d29cba lines for the pump, doorbell and svc_sem_write, defined vEP differently from doc 13 (which it names as the vocabulary authority), and called Design A prototypable in the 1.0 programme while M6 classifies the same prototype as post-1.0 research. Fix all three, refresh the status hash, and add the doc to the docs/ and wiki/ indexes with the renumbered reading-order rows. 2026-10-08T18:10:21+00:00 Arthur Hanson Rasmusson arthur@vgpu.io 2026-10-08T18:10:21+00:00 urn:sha1:236e63726c9a99e220d43475aa89ed8c06d719ef Line anchors drifted when a9d29cba landed after the doc was written at 0da66259 (svc_thread, svc_gr_request, svc_pending_add, the H3 guard, the readiness gate). Also: the grv5 SEMA_DBG=Y campaign showed the notifier and event wake-up do fire while the counter slot publication is the link that never writes, so the document's 'completion wake-up' framing was stale in the stage table, section 3.4, section 6.1, the challenges and the iteration plan; refresh the status hash, the discovery-cadence wording and the mode-matrix source note, and extend the change log. 2026-10-08T18:04:47+00:00 Arthur Hanson Rasmusson arthur@vgpu.io 2026-10-08T18:04:47+00:00 urn:sha1:c8ec65aeff12fb6b8bdc2c5028d247f1af6e6fe7 2026-10-08T17:51:22+00:00 Arthur Hanson Rasmusson arthur@vgpu.io 2026-10-08T17:51:22+00:00 urn:sha1:dc551a6bf1458f6a9d621ce97bd86607e38b1080 2026-10-08T17:41:31+00:00 Arthur Hanson Rasmusson arthur@vgpu.io 2026-10-08T17:41:31+00:00 urn:sha1:b7c5212f7691f71202a7c3661993354132429712 2026-10-06T19:18:39+00:00 Arthur Hanson Rasmusson arthur@vgpu.io 2026-10-06T19:18:39+00:00 urn:sha1:6b0673a21b1cb5493554c898181fe289355cadc0 New page docs/04-implementation/03-execution-frontier.md describes the chain that must fire for a guest CUDA launch (guest push -> GPFIFO/front-end -> inline launch-descriptor install -> engine read/dispatch -> completion), where the leading edge is (the descriptor install path), how we know (front-end vs engine-authored observables and their limits), what is exonerated (context validity at dispatch, destination window mapping, fetch alignment, shared-buffer rule, parenting), the ranked issues (verbatim prelude targets, missing descriptor-virtualization control, sentinel hygiene), live investigation lines and labelled theories. Align every page that still said GR execution is blocked on engine-context validity to the current frontier, and add the new page to the README reading order (row 15, later rows renumbered). Docs only; no code. 2026-10-06T00:08:06+00:00 Arthur Hanson Rasmusson arthur@vgpu.io 2026-10-06T00:08:06+00:00 urn:sha1:0ffde4d41eb43e69d8ba7b19780dcf51a8210eb1 2026-10-05T00:54:03+00:00 Arthur Hanson Rasmusson arthur@vgpu.io 2026-10-05T00:54:03+00:00 urn:sha1:e9e24b6b316e47ac443ee57ed043e3d410a56783 The grace-expiry fake path consumed a held CE entry without marking its GPFIFO slot as consumed for the put epoch, and the replay guard only ran while the channel was not deferring. A later pin-batch rewind then re-read the slot, found no recorded identity, and executed the push's copies against a staging buffer the client had refilled after the faked release - a deterministic vadd input shift (a[k] == h_a[k + 2 MB]). - grace-fake consume path now calls svc_replay_note() before advancing; - the svc_replay_seen() replay skip is evaluated unconditionally: a slot consumed in the current epoch is skipped on every replay, deferral or not, until a put wrap clears the mark; - the once-only identity gate gains a content witness (FNV-1a hash of the recorded push bytes): the same entry words with different push content is a new push (clients rewrite push buffers in place) and runs its ops with a cleared done bitmap; suppression requires identical content; - snapshot write-back persists the hash array; new drain counter reident= counts content-mismatch cancellations; - the grace window stays at 8 s: a faked entry's work is never run, so the hold is that work's only chance (a 2.5 s experiment made red-class runs complete with corrupt data instead of timing out). Verified: module 8e90fc7e..., three consecutive end-to-end acceptance runs (MAIL + VADD bad=0 checksum=392344090.500000 + STATUS OK). 2026-10-04T23:13:16+00:00 Arthur Hanson Rasmusson arthur@vgpu.io 2026-10-04T23:13:16+00:00 urn:sha1:25d41ed6f719eb243a5ef77ab558510820a57c73 A later supervised cycle reproduced the held-entry retry over a refilled staging buffer, the completed operation was skipped, and the end-to-end transfer verified byte-for-byte (bad=0, expected checksum). 2026-10-04T22:54:35+00:00 Arthur Hanson Rasmusson arthur@vgpu.io 2026-10-04T22:54:35+00:00 urn:sha1:a3367ec6c2658724f4dba1be2de4607302fba5f2 The pump's operand-targeted-scan hold decodes a push, runs every op that translates, then leaves the entry pending for a retry. The retry re-decoded the whole push and re-ran the operations that had already completed. A CE copy reads a client staging buffer the client refills per chunk, so the retry overwrote a finished chunk with the following chunk's data (observed: the bridge's vadd input half replaced by the next 1 MB chunk, first half of the device buffer byte-identical to the source shifted by exactly 2 MB; the same 1 MB copy logged twice with different staging contents). The service now records, per GPFIFO slot, the entry identity plus a bitmap of the decoded operation indexes whose work has executed for that identity, and a complete flag for a pass that ended with no operand pending. svc_run_ops skips already-executed ops on a retry and marks the rest as they succeed; the pump stores the record immediately after decode, before any hold path can break, so the pending path can no longer lose it. A replay of a complete identity suppresses all ops; a partial identity retries only what is owed. Also carries the ops_once diagnostic counter in the service snapshot line and documents the operation-granularity rule in the architecture doc.