summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorArthur Hanson Rasmusson <arthur@vgpu.io>2026-11-17 01:19:29 -0500
committerArthur Hanson Rasmusson <arthur@vgpu.io>2026-11-17 01:19:29 -0500
commit3a0a1eba404919951ca3333ae9492f7213e60f75 (patch)
treeada9df699ac9b0c7051e61dc3c73005e15c01225
parent1db3831e8f1c40f8e65e86dc38d457aa494c9172 (diff)
downloadopen-iov-3a0a1eba404919951ca3333ae9492f7213e60f75.tar.gz
open-iov-3a0a1eba404919951ca3333ae9492f7213e60f75.zip
docs(wiki): 2026-11-17 status refresh - real GPU-GL draw admitted/replayed; per-draw MME macro body is the gateHEADmaster
- 11 wiki pages refreshed: the offscreen EGL/GBM shim gives the guest a real NVIDIA GL context without Xorg/DDX; the real GZDoom draw window (12068 B at push 0x402f9d8, op=4 CALL(0) 0x3800 imm 0xd48 plus slots 44/57/58) is recognised, admitted bind-free, chunked and replayed verbatim. - CALL(0) executes without trapping (eng89t resolve through client SA[0] then golden, not-resident calls elided); c1026/c1027 entered the captured macro and c1027 reached the first DS with real stage data. Trap 0x80001528 decoded as a sticky TRAPPED_ADDR latch, not a cause/PC. - Remaining gate recorded precisely: the client's per-draw MME macro body was never captured (the prelude carries only the 12 setup macros), with the synthetic golden body the surviving wedge; stores still wrote=0, no px. - STATE-CURRENT.md snapshot prepended; wiki published to open-iov.org (revs 24221-24231; 68 pages audited, 0 problems).
-rw-r--r--STATE-CURRENT.md63
-rw-r--r--wiki/.publish-manifest.json110
-rw-r--r--wiki/Execution-Frontier.md77
-rw-r--r--wiki/Execution-Plane.md32
-rw-r--r--wiki/FAQ.md22
-rw-r--r--wiki/Graphics-Execution.md177
-rw-r--r--wiki/Host-Module.md28
-rw-r--r--wiki/OpenGL.md60
-rw-r--r--wiki/Physical-GPU-Backend.md26
-rw-r--r--wiki/Project-Goals.md6
-rw-r--r--wiki/Project-Plan.md34
-rw-r--r--wiki/Project-Status.md25
-rw-r--r--wiki/System-Overview.md18
13 files changed, 414 insertions, 264 deletions
diff --git a/STATE-CURRENT.md b/STATE-CURRENT.md
index f18d3be..e1275c7 100644
--- a/STATE-CURRENT.md
+++ b/STATE-CURRENT.md
@@ -1,5 +1,68 @@
# Open-IOV Current State
+> **Snapshot: 2026-11-17 ~01:20 (SESSION 157 continued; HEAD `1db3831e` ==
+> `vgpu/master`; the working tree carries only this docs refresh; supersedes
+> the 2026-11-16 ~22:55 entry below).**
+> The graphics front crossed the **real GPU-GL gate**: the guest now renders
+> through the real NVIDIA driver without Xorg/DDX, and the host admits,
+> chunks and replays the **real client draw**. The remaining wall is one
+> missing input — the client's per-draw MME macro body.
+>
+> - **Real NVIDIA GL in the guest, no Xorg/DDX.** An offscreen SDL EGL/GBM
+> shim (`GZ_EGL`, `tools/guest-diag/gz_es.c`) gives GZDoom a real NVIDIA
+> context: `GL_RENDERER: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2`,
+> `GL_VERSION: 4.6.0 NVIDIA 570.144` (not llvmpipe).
+> - **The real draw is decoded, admitted and replayed.** The GZDoom draw
+> window is 12068 B at push `0x402f9d8` (3017 words) and has no
+> `0x3910/0x3914`: its draw is an op=4 IMMD `CALL(0)` to method `0x3800`
+> (`imm=0xd48=3400`) plus CALL slots 44/57/58 (`0x3960/0x39c8/0x39d0`) and
+> 7x `0x1b00` inline uploads. It carries no colour-target bind, so
+> RT-gated admission had refused it; recognition now covers the real
+> marker, admission is bind-free, the CALL-bearing chunk is forced first,
+> and every chunk replays verbatim (c1025: `GL-FLUSH admitted=1`,
+> `DRAW-WRITE m=0x3800 op=4`, `3D chunk launch ... draw=1`,
+> `MME-CALL-ARGS slot=0 data=0xd48`, `MME-EXEC-CALL slot=0`).
+> - **`CALL(0)` executes without wedging.** eng89t resolves the immediate as
+> an IR address through client SA[0] (then golden) and elides a
+> not-resident op=4 CALL(0) to a NOP (`MME-CALL-UNMAPPED
+> reason=not-resident`). c1026/c1027 entered the captured macro
+> (`macro-status=00000004`, `mpc` 0->4) with no trap; c1027 reached the
+> first DS with real stage data (`DS-FAST2 ds_after=83044206
+> stage=015e0900,015e0a00,015c0400`). Trap `0x80001528` is decoded as a
+> sticky `NV_PGRAPH_TRAPPED_ADDR` latch (bit31 INVALID, subch 0, method
+> `0x1528` = `SET_SHADER_EXCEPTIONS`), not a cause/PC.
+> - **Remaining gap (precise): the per-draw MME macro body was never
+> captured.** The 59580-byte prelude carries only the 12 setup macros
+> (573 code words, pc 0..0x98); the draw push has no `0x114/0x11c`; and
+> `0xd48` is a macro length/argument, not an IR entry. The surviving wedge
+> is the synthetic golden body (`badf1201 pc=513 mac=0xf1`) on a
+> non-CALL(0) launch. Next: capture the per-draw `0x114` upload (every
+> beef push plus the X/2D channel) or implement/verify the MME64 body,
+> install it before the draw launch, then check `DS-FAST2 ds_after=8[01]`,
+> `GUEST-WIT va=0x15d`, `wrote>0`, `px0!=0`. No vGPU surface store or
+> pixel exists yet (`wrote=0`, no `px_nonblack`).
+> - **GZDoom software-GL video unchanged and verified** (Mesa llvmpipe; four
+> files, 22 s flight + 18 s orbit, 640x480/1280x960, 30 fps) at
+> `https://files.vgpu.io/files/open-iov-gzdoom-20261116` — a
+> guaranteed-quality deliverable, not a vGPU rendering claim.
+> - Commits since the last snapshot: `9386fe4b` (`phys_gr_dump_push`),
+> `10e03cd7` (eng89s: real `CALL(0)` `0x3800` draw + GZ_EGL harness),
+> `1db3831e` (eng89t: CALL(0) resolve + no-wedge fallback); HEAD
+> `1db3831e` == `vgpu/master`, working tree clean before this refresh.
+>
+> CUDA front unchanged (backgrounded while graphics holds the device; its
+> 10-30 status stands): `41343c63` green (`victory_mail` `VADD bad=0` +
+> `STATUS OK`; `vecadd_loop` 100 launches PASS); the fresh-boot battery's red
+> class is D2H-stage with release-discipline fixes staged; the SESSION 143
+> Vulkan fence regression is not re-measured.
+>
+> Live at check (read-only): host uptime 16 h 03 m (boot 2026-11-16 ~09:13);
+> the campaign finished its last cycle and the module was unloaded cleanly at
+> 00:09:59 (`nv_vgpu_exit` completed; no mdev, no QEMU; host idle); `nvidia`
+> stays loaded for the host's own GPU; pstore empty; no Xid/Oops; no reboot
+> initiated during the check. The open-iov.org wiki was refreshed alongside
+> this snapshot (11 pages, revs 24221-24231; 68 pages audited, 0 problems).
+>
> **Snapshot: 2026-11-16 ~22:55 (SESSION 157 continued; HEAD `a06d4b13` ==
> `vgpu/master`; the working tree carries only this docs refresh; supersedes
> the 2026-11-16 ~00:35 entry below).**
diff --git a/wiki/.publish-manifest.json b/wiki/.publish-manifest.json
index f0b58c6..20d76cd 100644
--- a/wiki/.publish-manifest.json
+++ b/wiki/.publish-manifest.json
@@ -64,11 +64,11 @@
},
"FAQ": {
"file": "FAQ.wiki",
- "new_revid": 24212,
- "old_revid": 24201,
- "source_sha": "b8c5ff6fbb6df549",
- "summary": "2026-11-16 evening status refresh: host-side draw chain proven end to end; guest draw submission is the remaining wall; software-GL GZDoom video noted as non-vGPU",
- "timestamp": "2026-11-17T03:53:52Z",
+ "new_revid": 24223,
+ "old_revid": 24212,
+ "source_sha": "e85e743aed4934a2",
+ "summary": "2026-11-17 status refresh: real NVIDIA GPU-GL draw admitted and replayed (CALL(0) 0x3800), CALL(0) executes without wedging; per-draw MME macro body is the remaining gate; software-GL video remains non-vGPU",
+ "timestamp": "2026-11-17T06:18:00Z",
"title": "FAQ"
},
"GMMU Multi-Tenant Protection": {
@@ -127,11 +127,11 @@
},
"Graphics Execution": {
"file": "Graphics-Execution.wiki",
- "new_revid": 24213,
- "old_revid": 24202,
- "source_sha": "8098340dc7ab9f35",
- "summary": "2026-11-16 evening status refresh: host-side draw chain proven end to end; guest draw submission is the remaining wall; software-GL GZDoom video noted as non-vGPU",
- "timestamp": "2026-11-17T03:53:52Z",
+ "new_revid": 24224,
+ "old_revid": 24213,
+ "source_sha": "0f31bea31b5f46bd",
+ "summary": "2026-11-17 status refresh: real NVIDIA GPU-GL draw admitted and replayed (CALL(0) 0x3800), CALL(0) executes without wedging; per-draw MME macro body is the remaining gate; software-GL video remains non-vGPU",
+ "timestamp": "2026-11-17T06:18:01Z",
"title": "Graphics Execution"
},
"Guest Driver Lifecycle: A Field Guide": {
@@ -226,11 +226,11 @@
},
"OpenGL": {
"file": "OpenGL.wiki",
- "new_revid": 24215,
- "old_revid": 24204,
- "source_sha": "3b37cb8e79d35dc4",
- "summary": "2026-11-16 evening status refresh: host-side draw chain proven end to end; guest draw submission is the remaining wall; software-GL GZDoom video noted as non-vGPU",
- "timestamp": "2026-11-17T03:54:01Z",
+ "new_revid": 24226,
+ "old_revid": 24215,
+ "source_sha": "195f0bc4b024f820",
+ "summary": "2026-11-17 status refresh: real NVIDIA GPU-GL draw admitted and replayed (CALL(0) 0x3800), CALL(0) executes without wedging; per-draw MME macro body is the remaining gate; software-GL video remains non-vGPU",
+ "timestamp": "2026-11-17T06:18:02Z",
"title": "OpenGL"
},
"Performance": {
@@ -244,38 +244,38 @@
},
"Physical GPU Backend and Guest Wiring": {
"file": "Physical-GPU-Backend.wiki",
- "new_revid": 24216,
- "old_revid": 24205,
- "source_sha": "7ef20e641634d8e2",
- "summary": "2026-11-16 evening status refresh: host-side draw chain proven end to end; guest draw submission is the remaining wall; software-GL GZDoom video noted as non-vGPU",
- "timestamp": "2026-11-17T03:54:02Z",
+ "new_revid": 24227,
+ "old_revid": 24216,
+ "source_sha": "3390dbe273c7b158",
+ "summary": "2026-11-17 status refresh: real NVIDIA GPU-GL draw admitted and replayed (CALL(0) 0x3800), CALL(0) executes without wedging; per-draw MME macro body is the remaining gate; software-GL video remains non-vGPU",
+ "timestamp": "2026-11-17T06:18:02Z",
"title": "Physical GPU Backend and Guest Wiring"
},
"Project Goals": {
"file": "Project-Goals.wiki",
- "new_revid": 24217,
- "old_revid": 24206,
- "source_sha": "bfe4d23f75dbc9c9",
- "summary": "2026-11-16 evening status refresh: host-side draw chain proven end to end; guest draw submission is the remaining wall; software-GL GZDoom video noted as non-vGPU",
- "timestamp": "2026-11-17T03:54:03Z",
+ "new_revid": 24228,
+ "old_revid": 24217,
+ "source_sha": "a83311835586282f",
+ "summary": "2026-11-17 status refresh: real NVIDIA GPU-GL draw admitted and replayed (CALL(0) 0x3800), CALL(0) executes without wedging; per-draw MME macro body is the remaining gate; software-GL video remains non-vGPU",
+ "timestamp": "2026-11-17T06:18:03Z",
"title": "Project Goals"
},
"Project Plan": {
"file": "Project-Plan.wiki",
- "new_revid": 24218,
- "old_revid": 24207,
- "source_sha": "5244de600de0129e",
- "summary": "2026-11-16 evening status refresh: host-side draw chain proven end to end; guest draw submission is the remaining wall; software-GL GZDoom video noted as non-vGPU",
- "timestamp": "2026-11-17T03:54:04Z",
+ "new_revid": 24229,
+ "old_revid": 24218,
+ "source_sha": "6c39471199029aae",
+ "summary": "2026-11-17 status refresh: real NVIDIA GPU-GL draw admitted and replayed (CALL(0) 0x3800), CALL(0) executes without wedging; per-draw MME macro body is the remaining gate; software-GL video remains non-vGPU",
+ "timestamp": "2026-11-17T06:18:03Z",
"title": "Project Plan"
},
"Project Status": {
"file": "Project-Status.wiki",
- "new_revid": 24219,
- "old_revid": 24208,
- "source_sha": "96a1beefe4fa981f",
- "summary": "2026-11-16 evening status refresh: host-side draw chain proven end to end; guest draw submission is the remaining wall; software-GL GZDoom video noted as non-vGPU",
- "timestamp": "2026-11-17T03:54:04Z",
+ "new_revid": 24230,
+ "old_revid": 24219,
+ "source_sha": "9980835e7167bcdc",
+ "summary": "2026-11-17 status refresh: real NVIDIA GPU-GL draw admitted and replayed (CALL(0) 0x3800), CALL(0) executes without wedging; per-draw MME macro body is the remaining gate; software-GL video remains non-vGPU",
+ "timestamp": "2026-11-17T06:18:04Z",
"title": "Project Status"
},
"RPC Message Format": {
@@ -289,11 +289,11 @@
},
"System Overview": {
"file": "System-Overview.wiki",
- "new_revid": 24220,
- "old_revid": 24209,
- "source_sha": "231c7ce3595a6865",
- "summary": "2026-11-16 evening status refresh: host-side draw chain proven end to end; guest draw submission is the remaining wall; software-GL GZDoom video noted as non-vGPU",
- "timestamp": "2026-11-17T03:54:05Z",
+ "new_revid": 24231,
+ "old_revid": 24220,
+ "source_sha": "434d2f7de1e1ebbc",
+ "summary": "2026-11-17 status refresh: real NVIDIA GPU-GL draw admitted and replayed (CALL(0) 0x3800), CALL(0) executes without wedging; per-draw MME macro body is the remaining gate; software-GL video remains non-vGPU",
+ "timestamp": "2026-11-17T06:18:05Z",
"title": "System Overview"
},
"Template:About message": {
@@ -325,11 +325,11 @@
},
"The Execution Frontier": {
"file": "Execution-Frontier.wiki",
- "new_revid": 24210,
- "old_revid": 24199,
- "source_sha": "14a2659a1847931f",
- "summary": "2026-11-16 evening status refresh: host-side draw chain proven end to end; guest draw submission is the remaining wall; software-GL GZDoom video noted as non-vGPU",
- "timestamp": "2026-11-17T03:53:50Z",
+ "new_revid": 24221,
+ "old_revid": 24210,
+ "source_sha": "7893928e0630a9f6",
+ "summary": "2026-11-17 status refresh: real NVIDIA GPU-GL draw admitted and replayed (CALL(0) 0x3800), CALL(0) executes without wedging; per-draw MME macro body is the remaining gate; software-GL video remains non-vGPU",
+ "timestamp": "2026-11-17T06:17:59Z",
"title": "The Execution Frontier"
},
"The Guest Stack and CUDASW": {
@@ -343,20 +343,20 @@
},
"The Host Module (vgsp.ko)": {
"file": "Host-Module.wiki",
- "new_revid": 24214,
- "old_revid": 24203,
- "source_sha": "a715873cdb2312b0",
- "summary": "2026-11-16 evening status refresh: host-side draw chain proven end to end; guest draw submission is the remaining wall; software-GL GZDoom video noted as non-vGPU",
- "timestamp": "2026-11-17T03:53:53Z",
+ "new_revid": 24225,
+ "old_revid": 24214,
+ "source_sha": "945cb9944fc9b8dc",
+ "summary": "2026-11-17 status refresh: real NVIDIA GPU-GL draw admitted and replayed (CALL(0) 0x3800), CALL(0) executes without wedging; per-draw MME macro body is the remaining gate; software-GL video remains non-vGPU",
+ "timestamp": "2026-11-17T06:18:01Z",
"title": "The Host Module (vgsp.ko)"
},
"The vGSP Execution Plane (vEP)": {
"file": "Execution-Plane.wiki",
- "new_revid": 24211,
- "old_revid": 24200,
- "source_sha": "27f9b22f9ec1b04c",
- "summary": "2026-11-16 evening status refresh: host-side draw chain proven end to end; guest draw submission is the remaining wall; software-GL GZDoom video noted as non-vGPU",
- "timestamp": "2026-11-17T03:53:51Z",
+ "new_revid": 24222,
+ "old_revid": 24211,
+ "source_sha": "ea5a3fb9be899432",
+ "summary": "2026-11-17 status refresh: real NVIDIA GPU-GL draw admitted and replayed (CALL(0) 0x3800), CALL(0) executes without wedging; per-draw MME macro body is the remaining gate; software-GL video remains non-vGPU",
+ "timestamp": "2026-11-17T06:18:00Z",
"title": "The vGSP Execution Plane (vEP)"
},
"UVM in the Guest": {
diff --git a/wiki/Execution-Frontier.md b/wiki/Execution-Frontier.md
index bfecad9..950902a 100644
--- a/wiki/Execution-Frontier.md
+++ b/wiki/Execution-Frontier.md
@@ -14,7 +14,7 @@
> [`../docs/04-implementation/03-execution-frontier.md`](../docs/04-implementation/03-execution-frontier.md);
> the docs tree wins on disagreement.
-Status: 2026-11-16, tree `master @ a06d4b13`.
+Status: 2026-11-17, tree `master @ 1db3831e`.
Tags: `[live]` observed; `[wip]` partial; `[wall]` current blocker; theories
are labelled as such.
@@ -144,19 +144,28 @@ chunks, a 128-slot candidate ring), the beef draw lane latches a **clean DS**
capture-less boots get a **golden 2799-word MME pack**, and
`MME-CALL-HOLD -> MME-CARRY-SAVE -> MME-CARRY-FIRE -> MME-PACK-REARM ->
MME-SA-REARM` fires with the prelude latch kept across the channel recycle.
-The **decisive finding is guest-side**: across 36 boots (c990-c1019) the
-client never submitted a non-null `CALL(34)` draw macro — every
-`0x3910/0x3914` hit is an interior method write with `data=0x0`, no CALL
-header exists in the admitted windows, and those cycles logged guest
-EGL/dri2 failures and OOM kills. The next work is guest-first (repair and
-verify the guest GL/EGL path and memory, then capture one real frame
-submission), followed by the vertex/store and the window/screen present
-path; the draw still does not store on the vGPU path (`wrote=0`, `0/1025`,
-`px0=0`), glxgears' window is black, a synchronous window draw can wedge X,
-and the per-boot X first-generation start lottery is the dominant throughput
-limiter. A GZDoom video was separately delivered through the guest's
-**software GL** path (Mesa llvmpipe) as a guaranteed-quality deliverable; it
-is not a vGPU rendering claim. The guest Vulkan
+The **late-11-16 wave crossed the guest submission gap**: an offscreen SDL
+EGL/GBM shim gives GZDoom a real NVIDIA GL context without Xorg/DDX
+(`GL_RENDERER: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2`, `GL_VERSION: 4.6.0
+NVIDIA 570.144`; no llvmpipe), and the real draw window surfaced — 12068 B
+at push `0x402f9d8`, an op=4 IMMD `CALL(0)` to method `0x3800` (`imm=0xd48`)
+plus slots 44/57/58 (`0x3960/0x39c8/0x39d0`), with no `0x3910/0x3914` and no
+colour-target bind of its own. Recognition covers the real marker, admission
+happens on the marker even without a bind, the CALL-bearing chunk is forced
+first and every chunk replays verbatim. `CALL(0)` no longer wedges: the
+immediate is resolved as an IR address through client SA[0] (then golden)
+and a not-resident call is elided to a NOP; c1026/c1027 entered the captured
+macro without trapping and c1027 produced the first DS with real stage data
+(`DS-FAST2 ds_after=83044206 stage=015e0900,015e0a00,015c0400`). The
+remaining gate is the client's **per-draw MME macro body**, never captured
+(the 59580-byte prelude carries only the 12 setup macros; the draw push has
+no `0x114/0x11c`), with the synthetic golden body the surviving wedge
+(`badf1201 pc=513 mac=0xf1`). The draw still does not store on the vGPU path
+(`wrote=0`, `0/1025`, `px0=0`), glxgears' window is black, a synchronous
+window draw can wedge X, and the per-boot X first-generation start lottery
+is the dominant throughput limiter. A GZDoom video was separately delivered
+through the guest's **software GL** path (Mesa llvmpipe) as a
+guaranteed-quality deliverable; it is not a vGPU rendering claim. The guest Vulkan
pipeline's inline-to-memory upload arm is its gap. The full picture lives on
[`Graphics-Execution.md`](Graphics-Execution.md).
@@ -231,16 +240,20 @@ the beef draw lane latches a **clean DS** (`DS-FAST2 ... ds_after=80000000`,
c963) at the live-derived GS attribute map, capture-less boots get a
**golden 2799-word MME pack**, and
`MME-CALL-HOLD -> MME-CARRY-FIRE -> MME-PACK-REARM -> MME-SA-REARM` fires
-with the prelude latch kept across the channel recycle. The **decisive
-finding is guest-side**: across 36 boots (c990-c1019) the client never
-submitted a non-null `CALL(34)` draw macro — every `0x3910/0x3914` hit is an
-interior method write with `data=0x0`, no CALL header exists in the admitted
-windows, and the same cycles logged guest EGL/dri2 failures and OOM kills.
-A GZDoom video was separately delivered through the guest's **software GL**
-path (Mesa llvmpipe) as a guaranteed-quality deliverable; it is not a vGPU
-rendering claim. The next work is guest-first (a real draw submission), then
-the vertex/store, the window/screen present, and the per-boot X
-first-generation start lottery
+with the prelude latch kept across the channel recycle. The **late-11-16
+wave crossed the guest submission gap**: an offscreen EGL/GBM shim gives
+GZDoom a real NVIDIA GL context without Xorg/DDX, the real op=4 `CALL(0)`
+`0x3800` draw is admitted and replayed (12068 B at push `0x402f9d8`), and
+`CALL(0)` executes its captured macro without trapping (eng89t resolves the
+immediate through client SA[0]/golden and elides not-resident calls to
+NOPs); c1027 reached the first DS with real stage data. The remaining gate
+is the client's per-draw MME macro body, never captured (the prelude carries
+only the 12 setup macros; the draw push has no `0x114/0x11c`), with the
+synthetic golden body the surviving wedge (`badf1201`). A GZDoom video was
+separately delivered through the guest's **software GL** path (Mesa
+llvmpipe) as a guaranteed-quality deliverable; it is not a vGPU rendering
+claim. The next work is the per-draw macro body, then the vertex/store, the
+window/screen present, and the per-boot X first-generation start lottery
([`Graphics-Execution.md`](Graphics-Execution.md)).
## 6. Lines of investigation (live)
@@ -255,14 +268,14 @@ first-generation start lottery
4. **Hold the acceptance battery** — vector-add, matrix-multiply and the
transformer kernel; each entry is accepted only on its own verification
output (`bad=0` + `STATUS OK`).
-5. **The graphics pixel frontier** — the released replay now executes the
- draw macro (`DRAW_IAB`, `mac=0x22`, TCS-off DS clean, synthetic viewport,
- chained release); next identify the draw's true vertex buffer (no captured
- client push binds it; the eng71 scan candidate is a heuristic), make the
- render-target store/alias visible (`GUEST-WIT` coverage of the big-surface
- alias pages) so the draw stores (`wrote>0`) at the bound render target,
- then make the window/screen present land, and reduce the per-boot
- binding/X start lottery so the proven off-screen frames become
+5. **The graphics pixel frontier** — the real guest GL draw is now
+ submitted, admitted and replayed (`CALL(0)` `0x3800`, no wedge, first DS
+ with real stage data); next capture/verify the client's per-draw MME
+ macro body (the prelude carries only the setup macros) so the real body
+ executes instead of the synthetic golden one, then make the
+ render-target store visible (`GUEST-WIT` surface pages) so the draw
+ stores (`wrote>0`), then make the window/screen present land, and reduce
+ the per-boot X start lottery so the proven off-screen frames become
window pixels; the lanes, the walls and the milestone ladder are on
[`Graphics-Execution.md`](Graphics-Execution.md).
diff --git a/wiki/Execution-Plane.md b/wiki/Execution-Plane.md
index d8786dd..b84f16f 100644
--- a/wiki/Execution-Plane.md
+++ b/wiki/Execution-Plane.md
@@ -8,7 +8,7 @@
> when the two disagree, the docs tree wins. Front door:
> [`../docs/README.md`](../docs/README.md).
-Status: 2026-11-16, tree `master @ a06d4b13`. Tags: `[live]` proven with the
+Status: 2026-11-17, tree `master @ 1db3831e`. Tags: `[live]` proven with the
stock guest driver; `[gated]` implemented, default-off or parameter-gated;
`[wip]` partial; `[wall]` current blocker; `[target]` named success latch;
`[planned]` designed, not built.
@@ -169,19 +169,23 @@ guest: push + QMD + GPFIFO entry + doorbell (BAR0 0x88704)
c963) at the live-derived GS attribute map, capture-less boots get a
**golden 2799-word MME pack**, and `MME-CALL-HOLD -> MME-CARRY-SAVE ->
MME-CARRY-FIRE -> MME-PACK-REARM -> MME-SA-REARM` fires with the prelude
- latch kept across the channel recycle. The **decisive finding is
- guest-side**: across 36 boots (c990-c1019) the client never submitted a
- non-null `CALL(34)` draw macro — every `0x3910/0x3914` hit is an interior
- method write with `data=0x0`, no CALL header exists in the admitted
- windows, and those cycles logged guest EGL/dri2 failures and OOM kills.
- No non-black **window/screen** frame has been produced through the NVIDIA
- path yet: the next work is guest-first (a real draw submission), then the
- vertex/store and the window/screen present, with the per-boot X
- first-generation lottery as the throughput limiter. A GZDoom video was
- separately delivered through the guest's **software GL** path (Mesa
- llvmpipe) as a guaranteed-quality deliverable; it is not a vGPU rendering
- claim.Those are the
- named blockers. The lanes and the ladder are on
+ latch kept across the channel recycle. The **late-11-16
+ wave crossed the guest submission gap**: an offscreen EGL/GBM shim gives
+ GZDoom a real NVIDIA GL context without Xorg/DDX, and the real op=4
+ `CALL(0)` `0x3800` draw is admitted and replayed; `CALL(0)` executes its
+ captured macro without trapping (the immediate resolves through client
+ SA[0] then golden, and not-resident calls are elided), and c1027 reached
+ the first DS with real stage data. The remaining gate is the client's
+ per-draw MME macro body, never captured (the prelude carries only the 12
+ setup macros; the draw push has no `0x114/0x11c`), with the synthetic
+ golden body the surviving wedge (`badf1201`). No non-black
+ **window/screen** frame has been produced through the NVIDIA path yet:
+ the next work is that macro body, then the vertex/store and the
+ window/screen present, with the per-boot X first-generation lottery as the
+ throughput limiter. A GZDoom video was separately delivered through the
+ guest's **software GL** path (Mesa llvmpipe) as a guaranteed-quality
+ deliverable; it is not a vGPU rendering claim. Those are the named
+ blockers. The lanes and the ladder are on
[`Graphics-Execution.md`](Graphics-Execution.md).
## 6. Portability
diff --git a/wiki/FAQ.md b/wiki/FAQ.md
index e64ce2f..4fccb4e 100644
--- a/wiki/FAQ.md
+++ b/wiki/FAQ.md
@@ -5,7 +5,7 @@
> [`../docs/09-reference/glossary-and-faq.md`](../docs/09-reference/glossary-and-faq.md);
> the docs tree wins on disagreement.
-Status: 2026-11-16, tree `master @ a06d4b13`.
+Status: 2026-11-17, tree `master @ 1db3831e`.
## Project and positioning
@@ -61,13 +61,19 @@ candidate ring), the beef draw lane latches a **clean DS**
map, capture-less boots get a **golden 2799-word MME pack**, and
`MME-CALL-HOLD -> MME-CARRY-SAVE -> MME-CARRY-FIRE -> MME-PACK-REARM ->
MME-SA-REARM` fires with the prelude latch kept across the channel recycle.
-The **decisive finding is guest-side**: across 36 boots (c990-c1019) the
-client never submitted a non-null `CALL(34)` draw macro — every
-`0x3910/0x3914` hit is an interior method write with `data=0x0`, no CALL
-header exists in the admitted windows, and those cycles logged guest
-EGL/dri2 failures and OOM kills. Window and screen pixels are still the
-wall: the next work is guest-first (repair and verify the guest GL/EGL path
-and memory, then capture one real draw submission), followed by the
+The **late-11-16 wave crossed the guest submission gap**: an offscreen SDL
+EGL/GBM shim gives GZDoom a real NVIDIA GL context without Xorg/DDX
+(`GL_RENDERER: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2`, `GL_VERSION: 4.6.0
+NVIDIA 570.144`; no llvmpipe), and the real draw window surfaced — 12068 B
+at push `0x402f9d8`, an op=4 `CALL(0)` to method `0x3800` (`imm=0xd48`) plus
+slots 44/57/58 — and is admitted, chunked and replayed verbatim. `CALL(0)`
+no longer wedges: eng89t resolves the immediate through client SA[0] (then
+golden) and elides not-resident calls to NOPs; c1026/c1027 entered the
+captured macro without trapping and c1027 produced the first DS with real
+stage data. Window and screen pixels are still the wall: the remaining gate
+is the client's per-draw MME macro body, never captured (the prelude carries
+only the 12 setup macros; the draw push has no `0x114/0x11c`), with the
+synthetic golden body the surviving wedge (`badf1201`); then the
vertex/store and the window/screen present, with the per-boot X
first-generation start lottery as the throughput limiter. A GZDoom video was
separately delivered through the guest's **software GL** path (Mesa
diff --git a/wiki/Graphics-Execution.md b/wiki/Graphics-Execution.md
index 6cadc98..217cb13 100644
--- a/wiki/Graphics-Execution.md
+++ b/wiki/Graphics-Execution.md
@@ -12,7 +12,7 @@
> [`../docs/04-implementation/04-real-render-walls.md`](../docs/04-implementation/04-real-render-walls.md)
> (the measured walls); the docs tree wins on disagreement.
-Status: 2026-11-16, tree `master @ a06d4b13`. Tags: `[live]` observed end to
+Status: 2026-11-17, tree `master @ 1db3831e`. Tags: `[live]` observed end to
end; `[wip]` partially built; `[wall]` current blocker; `[target]` defined
success state; `[planned]` designed, not built.
@@ -161,46 +161,48 @@ fidelity:
`MME-PRELUDE`), and the chain `MME-CALL-HOLD -> MME-CARRY-SAVE ->
MME-CARRY-FIRE -> MME-PACK-REARM -> MME-SA-REARM` fires; the prelude latch
survives the per-fire channel recycle (`MME-LATCH-KEEP`) and every
- admitted-window chunk is forwarded in order. **The decisive finding is
- guest-side**: across 36 boots (c990-c1019) the client never submits a
- non-null `CALL(34)` draw macro — every `0x3910/0x3914` hit is an interior
- method write with `data=0x0`, no CALL header exists in the admitted
- windows (`DRAW-SCAN-PRE` found=0), and the same cycles logged guest
- EGL/dri2 failures and OOM kills, so the guest GL path was not producing a
- real draw submission. A GZDoom video (four files, 22 s flight + 18 s
- orbit, 640x480/1280x960, 30 fps, byte-verified) was delivered through the
- guest's **software GL** path (Mesa llvmpipe) as a guaranteed-quality
- deliverable — not a vGPU rendering claim. Stores on the vGPU path still
- miss (`wrote=0`, `0/1025` pages, `px0=0`); the window/screen present is
- still the frontier (§6), and the pack-completion and X-start lotteries
- remain the throughput limiters.
- **The real client draw uses `CALL_MME_MACRO(0)`.** The real-NVIDIA-GL
- capture (c1021/c1022) shows the 12068-byte draw window at push
- `0x402f9d8` carries no `0x3910/0x3914` write. Its draw is an IMMD (op 4)
- write to method `0x3800` (`hdr=8d480e00`, `imm=0xd48` = 3400), followed
- by CALL slots 44/57/58 (`0x3960`, `0x39c8`, `0x39d0`). That window also
- carries no colour-target bind of its own and no persisted bind was live,
- so the RT-gated admission refused it and it retired through the
- compute-QMD lane (`stream_3d=false`). Recognition now covers the real
- marker: `0x3800` (op 4; `imm>=0x100` as the admission floor) plus
- `0x3960/0x39c8/0x39d0`, with `0x3910/0x3914` kept; the call-0 predicate
- scans the admitted window (`start_off..at_off`) because a pre-window run
- header can swallow the window head (word 316's op=0 count=1059 covers
- words 400..1459 and hides the CALL at word 655 from a from-zero walk).
- Admission is on the real marker even without a bind, the chunk carrying
- the CALL is forced first (`draw_slice=1`, order 0), and every chunk is
- replayed verbatim. The CALL is not interpreted in software: the emitted
- window is walked by the physical GR front-end (the `0x114` prelude
- uploads precede the window in the same launch), and
- `MME-EXEC-CALL slot=0 ... op=4 imm=...` records the call reaching the
- emitted stream. c1025 receipts: `GL-FLUSH ... admitted=1`,
+ admitted-window chunk is forwarded in order. **The late-11-16 wave crossed the guest submission gap.** An offscreen
+ SDL EGL/GBM shim (`GZ_EGL`) gives the guest a real NVIDIA GL context
+ without Xorg/DDX (`GL_RENDERER: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2`,
+ `GL_VERSION: 4.6.0 NVIDIA 570.144` — no llvmpipe). The real GZDoom draw
+ window then surfaced: 12068 B at push `0x402f9d8` (3017 words), carrying
+ no `0x3910/0x3914` write. Its draw is an IMMD (op 4) CALL to method
+ `0x3800` (`imm=0xd48` = 3400) plus CALL slots 44/57/58 (`0x3960`,
+ `0x39c8`, `0x39d0`), 7x `0x1b00` inline uploads, and state words. The
+ window carries no colour-target bind of its own, so RT-gated admission
+ had refused it (it retired through the compute-QMD lane); recognition now
+ covers the real marker (`0x3800` op=4 with `imm>=0x100`, plus the three
+ secondaries; `0x3910/0x3914` kept), admission happens on the real marker
+ even without a bind, the CALL-bearing chunk is forced first, and every
+ chunk is replayed verbatim. c1025 receipts: `GL-FLUSH ... admitted=1`,
`DRAW-WRITE ... m=0x3800 op=4 data=0xd48`, `3D mark admitted (CALL(0)
- 0x3800 draw marker)`, `3D stream chunked`, `3D chunk launch ... draw=1`,
- `MME-CALL-ARGS slot=0 data=0xd48`, `MME-EXEC-CALL slot=0 ... imm=0xd48`.
- The captured SA[0] is still unresolved (`addr=0x0`), the exact
- 12068-byte window's post-fix admission was not re-captured (the run
- wedged on an earlier draw window first), and stores / `DRAW_IAB
- mac=0x22` remain the open frontier.
+ 0x3800 draw marker)`, `3D stream chunked` (4 chunks), `3D chunk launch
+ ... draw=1`, `MME-CALL-ARGS slot=0 data=0xd48`, `MME-EXEC-CALL slot=0`.
+ **CALL(0) no longer wedges**: eng89t resolves the CALL(0) immediate as an
+ IR address through the client SA[0] (then golden) and elides an op=4
+ CALL(0) whose body is not resident for this launch to a NOP
+ (`MME-CALL-UNMAPPED ... reason=not-resident`) so the ladder continues.
+ On c1026/c1027 the real draw's CALL(0) entered its captured macro
+ (`macro-status=00000004`, `mpc` 0->4) without trapping, and c1027
+ produced the first DS with real stage data (`DS-FAST2
+ ds_after=83044206 stage=015e0900,015e0a00,015c0400`). The trap code
+ `0x80001528` is decoded as the sticky `NV_PGRAPH_TRAPPED_ADDR` latch
+ (bit31 INVALID, subch 0, method `0x1528` = `SET_SHADER_EXCEPTIONS`), not
+ a cause/PC; the surviving wedge is the synthetic golden macro body
+ (`badf1201 pc=513 mac=0xf1`) on a non-CALL(0) launch. **Remaining gap
+ (precise):** the client's per-draw MME macro body was never captured —
+ the 59580-byte prelude carries only the 12 setup macros (573 code words,
+ pc 0..0x98), the draw push has no `0x114/0x11c`, and `0xd48` is a macro
+ length/argument, not an IR entry. The engine has the real draw method
+ stream but not the body to execute. Next: capture the per-draw `0x114`
+ upload (every beef push plus the X/2D channel) or implement/verify the
+ MME64 body, install it before the draw launch, then check `DS-FAST2
+ ds_after=8[01]`, `GUEST-WIT va=0x15d`, `wrote>0`, `px0!=0`. No vGPU
+ surface store or pixel is proven yet (`wrote=0`, no `px_nonblack`). The
+ software-GL GZDoom video (four files, 22 s flight + 18 s orbit,
+ 640x480/1280x960, 30 fps, byte-verified) remains the guaranteed-quality
+ deliverable and is not a vGPU rendering claim; the pack-completion and
+ X-start lotteries still gate run rate.
## 4. The channel and object picture
* **Every submission lives on a channel**: a GPFIFO ring plus engine objects,
@@ -263,9 +265,12 @@ swaps, and the GR backend no longer times out (the pair-close/pair-safe
replay executes the `DRAW_IAB` (`mac=0x22`) with a synthetic viewport, and
the 11-16 wave proved the whole host chain deterministic (admission of the
real pushes, clean DS, golden pack, CALL hold, carry fire, SA re-arm). The
- remaining question is now guest-side — a real non-null `CALL(34)` draw
- submission — after which the vertex/store and the window/screen present
- path are next.
+ late-11-16 wave then crossed the guest submission gap: a real NVIDIA EGL
+ context without Xorg/DDX, the real GZDoom op=4 `CALL(0)` `0x3800` draw
+ admitted and replayed, `CALL(0)` entering its captured macro without
+ trapping, and the first DS with real stage data. The remaining gate is
+ the client's per-draw MME macro body (never captured), then the
+ vertex/store and the window/screen present.
During bring-up the module also carries a **diagnostics-only mirror** for apps
that spin on a shared progress word; it exists so a run can proceed while the
@@ -274,34 +279,43 @@ requires it switched off, along with any external poke.
## 6. Where the frontier is (ranked walls)
-1. **Guest draw submission and the direct-GL store** `[wall]`. The
- **host-side chain is proven end to end** (2026-11-16): the real frame
- pushes are admitted (persisted colour-target bind from an earlier trusted
- push; draw markers accepted inside counted method runs; the 14.8-thousand-
- word window admitted and replayed as 40 chunks with a data-led start snap
- and a 128-slot candidate ring), the beef draw lane latches a **clean DS**
- (`DS-FAST2 ... ds_after=80000000`, c963) at the live-derived GS attribute
- map, capture-less boots get a **golden 2799-word MME pack** from the
- golden library, and `MME-CALL-HOLD -> MME-CARRY-SAVE -> MME-CARRY-FIRE ->
- MME-PACK-REARM -> MME-SA-REARM` fires with the prelude latch kept across
- the per-fire channel recycle; chunks are forwarded in order. The decisive
- finding of c990-c1019 (36 boots) is **guest-side**: the client never
- submits a non-null `CALL(34)` draw macro — every `0x3910/0x3914` hit is an
- interior method write with `data=0x0`, no CALL header exists in the
- admitted windows (`DRAW-SCAN-PRE` found=0), and those cycles logged guest
- EGL/dri2 failures and OOM kills, so the guest GL path was not producing a
- real draw submission in that boot class. The next work is guest-first
- (repair/verify the guest EGL/dri2 path and memory, only then capture one
- frame's submission); `MME-CALL-ARGS slot=34 data=`, `slot34=1`,
- `mac=0x22`, `VA=0xd74` and colour pages at `0x15d...` are the acceptance
- receipts. Closed on the way: the QMD-carrier theory (refuted: no QMD bit
- in the entry format, no QMD magic in 256 MiB BAR1), RT routing (the clear
- targets RT0 while the window binds RT1; RT0 bind verified 16x with correct
- target/geometry, still 61/61 `wrote=0`), and the `CODESRC` fault-park class
- (suspect program page relocated to the engine-mapped window-0 shadow,
- `17c7ed7c`; validated boot: 31 relocations, 51 GR launches, 79 GP_GET
- advances, 0 `FAULT_PDE`, 0 `WEDGE-REARM`, `backend_ok=35`). Stores on the
- vGPU path still miss (`wrote=0`, `0/1025`, `px0=0`).
+1. **The per-draw MME macro body and the store** `[wall]`. The
+ **host-side chain is proven end to end** and the **guest submission gap
+ was crossed late on 2026-11-16**: an offscreen SDL EGL/GBM shim (`GZ_EGL`)
+ gives the guest a real NVIDIA GL context without Xorg/DDX
+ (`GL_RENDERER: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2`,
+ `GL_VERSION: 4.6.0 NVIDIA 570.144`), and the real GZDoom draw window
+ surfaced — 12068 B at push `0x402f9d8`, an op=4 IMMD CALL to method
+ `0x3800` (`imm=0xd48=3400`) plus CALL slots 44/57/58
+ (`0x3960/0x39c8/0x39d0`), with no colour-target bind of its own.
+ Recognition now covers that real marker, admission happens on the marker
+ even without a bind, the CALL-bearing chunk is forced first, and every
+ chunk replays verbatim (c1025: `GL-FLUSH admitted=1`, `DRAW-WRITE
+ m=0x3800 op=4 data=0xd48`, `3D chunk launch ... draw=1`,
+ `MME-CALL-ARGS slot=0 data=0xd48`, `MME-EXEC-CALL slot=0`). **CALL(0) no
+ longer wedges**: eng89t resolves the immediate as an IR address through
+ the client SA[0] (then golden) and elides a not-resident op=4 CALL(0) to
+ a NOP (`MME-CALL-UNMAPPED ... reason=not-resident`); c1026/c1027 entered
+ the captured macro (`macro-status=00000004`, `mpc` 0->4) without
+ trapping, and c1027 produced the first DS with real stage data
+ (`DS-FAST2 ds_after=83044206 stage=015e0900,015e0a00,015c0400`). The trap
+ code `0x80001528` is a sticky `NV_PGRAPH_TRAPPED_ADDR` latch (bit31
+ INVALID, subch 0, method `0x1528` = `SET_SHADER_EXCEPTIONS`), not a
+ cause/PC; the surviving wedge is the synthetic golden macro body
+ (`badf1201 pc=513 mac=0xf1`) on a non-CALL(0) launch. **The remaining
+ gap is the client's per-draw MME macro body**, which was never captured:
+ the 59580-byte prelude carries only the 12 setup macros (573 code words,
+ pc 0..0x98), the draw push has no `0x114/0x11c`, and `0xd48` is a macro
+ length/argument, not an IR entry. Next: capture the per-draw `0x114`
+ upload (every beef push plus the X/2D channel) or implement/verify the
+ MME64 body, install it before the draw launch, then check `DS-FAST2
+ ds_after=8[01]`, `GUEST-WIT va=0x15d`, `wrote>0`, `px0!=0`. Stores on
+ the vGPU path still miss (`wrote=0`, `0/1025`, `px0=0`). Closed on the
+ way: the QMD-carrier theory (refuted), RT routing (the clear targets RT0
+ while the window binds RT1; RT0 bind verified 16x, still 61/61
+ `wrote=0`), and the `CODESRC` fault-park class (`17c7ed7c`; validated
+ boot: 31 relocations, 51 GR launches, 79 GP_GET advances, 0 `FAULT_PDE`,
+ 0 `WEDGE-REARM`, `backend_ok=35`).
2. **Window/screen present** `[wall]`. The pbuffer and off-screen frame paths
are proven (`pixel=ff0000ff`, 500/500 non-black frames, captured videos),
but a windowed present does not land: glxgears' window is black, the DDX
@@ -372,7 +386,10 @@ requires it switched off, along with any external poke.
| Real frame pushes admitted: persisted colour-target bind from an earlier trusted push (`RT-PERSIST`), draw markers accepted inside counted method runs, 14.8-thousand-word window admitted and replayed as 40 chunks (`3D stream chunked ... -> 40 chunk(s)`), data-led start snap (`WIN-START-SNAP`), 128-slot candidate ring | `[live]` |
| Clean DS on the beef draw lane after the full-window chunking (`DS-FAST2 ... ds_after=80000000`, c963) at the live-derived GS attribute map (maps=6), no SPH18; draw anchor after the first `0x3810` and raster enables emitted | `[live]` |
| Golden 2799-word MME pack on capture-less boots (`MME-GOLDEN overlay`, `MME-PRELUDE pack ir_words=2799`); `MME-CALL-HOLD -> MME-CARRY-SAVE -> MME-CARRY-FIRE -> MME-PACK-REARM -> MME-SA-REARM` fires; prelude latch kept across the per-fire channel recycle (`MME-LATCH-KEEP`); admitted-window chunks forwarded in order | `[live]` |
-| Guest draw submission: across 36 boots (c990-c1019) the client never submits a non-null `CALL(34)` draw macro — every `0x3910/0x3914` hit is an interior method write with `data=0x0`; no CALL header in the admitted windows (`DRAW-SCAN-PRE` found=0); guest EGL/dri2 failures and OOM kills in the same cycles; stores `wrote=0` / `0/1025` | `[wall]` |
+| Guest GL submission crossed (late 11-16): offscreen SDL EGL/GBM shim (`GZ_EGL`) gives GZDoom a real NVIDIA GL context without Xorg/DDX (`GL_RENDERER: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2`, `GL_VERSION: 4.6.0 NVIDIA 570.144`; no llvmpipe) | `[live]` |
+| Real GZDoom draw decoded and admitted: 12068 B window at push `0x402f9d8`, op=4 IMMD CALL to method `0x3800` (`imm=0xd48`) plus slots 44/57/58 (`0x3960/0x39c8/0x39d0`), no `0x3910/0x3914`; marker recognition, bind-free admission, draw-chunk-first, verbatim chunk replay (`3D chunk launch ... draw=1`) | `[live]` |
+| `CALL(0)` executes without trapping: immediate resolved as an IR address through client SA[0] then golden (`MME-CALL-RESOLVE`), not-resident calls elided (`MME-CALL-UNMAPPED ... reason=not-resident`); c1026/c1027 entered the captured macro (`macro-status=00000004`, mpc 0->4), first DS with real stage data (`DS-FAST2 ds_after=83044206 stage=015e0900,015e0a00,015c0400`); trap `0x80001528` decoded as a sticky TRAPPED_ADDR latch, not a cause/PC | `[live]` |
+| Per-draw MME macro body: never captured (the 59580-B prelude carries only the 12 setup macros, 573 code words pc 0..0x98; the draw push has no `0x114/0x11c`; `0xd48` is a length/argument, not an IR entry); the surviving wedge is the synthetic golden body (`badf1201 pc=513 mac=0xf1`) on a non-CALL(0) launch; stores `wrote=0`, no `px_nonblack` | `[wall]` |
| GZDoom video via the guest **software GL** path (Mesa llvmpipe): four byte-verified files (22 s flight + 18 s orbit, 640x480/1280x960, 30 fps) — a guaranteed-quality deliverable, **not** a vGPU rendering claim | `[live]` (software path) |
| Pack-completion and shallow-boot lotteries gate the deterministic release (throughput limiters) | `[wip]` |
| Window/screen present produces non-black window pixels | `[wall]` |
@@ -395,12 +412,16 @@ requires it switched off, along with any external poke.
GZDoom.
* Display/KMS bring-up (NvKms, `/dev/dri`, X, a real GL context) is not a
rendered-frame claim. GZDoom reaching `V_Init: allocate screen` proves the
- client's GL init and the direct-GL GR lane, not the game loop or a
- presented frame; the host-side chain is proven end to end (admission,
- clean DS, golden pack, CALL hold, carry fire, SA re-arm), but the decisive
- 11-16 finding is that the client did not submit a non-null `CALL(34)` draw
- macro in the recorded boots, so the stores are still missing and the
- window stays black.
+ client's GL init, not the game loop or a presented frame. The late-11-16
+ wave went further — a real NVIDIA GL context without Xorg/DDX, the real
+ op=4 CALL(0) draw admitted and replayed, `CALL(0)` entering its captured
+ macro without trapping, and a clean DS with real stage data — but the
+ client's per-draw MME macro body was never captured, the surviving wedge
+ is the synthetic golden body, and no surface store or pixel exists yet
+ (`wrote=0`, no `px_nonblack`), so the window stays black.
+* The real-NVIDIA EGL context is a guest-GL-path result, not a vGPU pixel
+ result: it proves the guest's GL stack now submits through the emulated
+ device, not that the draw's stores reached a render target.
* The engine-zero-write (NOWRITE) campaign is not a rendering result: it and
the draw census together proved the submission is macro-driven (no
method-grammar draw header exists), that RT routing is not the cause, and
diff --git a/wiki/Host-Module.md b/wiki/Host-Module.md
index 981c371..2291ad7 100644
--- a/wiki/Host-Module.md
+++ b/wiki/Host-Module.md
@@ -6,7 +6,7 @@
> source: [`../docs/03-architecture/06-host-module-and-hybrid-model.md`](../docs/03-architecture/06-host-module-and-hybrid-model.md);
> the docs tree wins on disagreement with this page.
>
-> Status: 2026-11-16, tree `master @ a06d4b13`. Tags: `[live]` observed with
+> Status: 2026-11-17, tree `master @ 1db3831e`. Tags: `[live]` observed with
> the stock guest driver; `[wip]` demonstrated live, being productized;
> `[gated]` implemented default-off behind supervised gates; `[wall]` known
> blocking limit; `[target]` designed, not built; `[planned]` roadmap.
@@ -147,17 +147,25 @@ live-derived GS attribute map, capture-less boots get a **golden 2799-word
MME pack** built from the golden library, and `MME-CALL-HOLD ->
MME-CARRY-SAVE -> MME-CARRY-FIRE -> MME-PACK-REARM -> MME-SA-REARM` fires
with the prelude latch kept across the per-fire channel recycle
-(`MME-LATCH-KEEP`); admitted-window chunks are forwarded in order. The
-**decisive finding is guest-side**: across 36 boots (c990-c1019) the client
-never submitted a non-null `CALL(34)` draw macro — every `0x3910/0x3914` hit
+(`MME-LATCH-KEEP`); admitted-window chunks are forwarded in order. At that point the decisive finding was
+guest-side: across 36 boots (c990-c1019) the client never submitted a
+non-null `CALL(34)` draw macro — every `0x3910/0x3914` hit
is an interior method write with `data=0x0`, no CALL header exists in the
admitted windows, and those cycles logged guest EGL/dri2 failures and OOM
-kills. So the next work is guest-first (a real draw submission), then the
-vertex/store and the window/screen present; the vGPU path still stores
-nothing (`wrote=0`, `px0=0`) and the window stays black or wedges X. A
-GZDoom video was separately delivered through the guest's **software GL**
-path (Mesa llvmpipe) as a guaranteed-quality deliverable; it is not a vGPU
-rendering claim.
+kills. The **late-11-16 wave crossed the guest submission gap**: an
+offscreen EGL/GBM shim gives GZDoom a real NVIDIA GL context without
+Xorg/DDX, the real op=4 `CALL(0)` `0x3800` draw is admitted and replayed,
+`CALL(0)` executes its captured macro without trapping (the immediate
+resolves through client SA[0] then golden; not-resident calls are elided),
+and the first DS with real stage data is reached. The remaining gate is the
+client's per-draw MME macro body, never captured (the prelude carries only
+the 12 setup macros; the draw push has no `0x114/0x11c`), with the synthetic
+golden body the surviving wedge (`badf1201`). The next work is that macro
+body, then the vertex/store and the window/screen present; the vGPU path
+still stores nothing (`wrote=0`, `px0=0`) and the window stays black or
+wedges X. A GZDoom video was separately delivered through the guest's
+**software GL** path (Mesa llvmpipe) as a guaranteed-quality deliverable; it
+is not a vGPU rendering claim.
## 6. Debug parameters
diff --git a/wiki/OpenGL.md b/wiki/OpenGL.md
index 62f9a01..eec40d9 100644
--- a/wiki/OpenGL.md
+++ b/wiki/OpenGL.md
@@ -12,7 +12,7 @@
> [`../docs/03-architecture/02-guest-stack-and-cudasw.md`](../docs/03-architecture/02-guest-stack-and-cudasw.md)
> (the guest stack). The docs tree wins on disagreement.
-Status: 2026-11-16, tree `master @ a06d4b13`. Tags: `[live]` observed with the
+Status: 2026-11-17, tree `master @ 1db3831e`. Tags: `[live]` observed with the
stock guest driver; `[wip]` partial; `[wall]` current blocker; `[target]`
defined success state.
@@ -109,7 +109,10 @@ Rated honestly, against the milestone ladder in the plan:
| Real frame pushes admitted: persisted colour-target bind from an earlier trusted push (`RT-PERSIST`), draw markers accepted inside counted method runs, 14.8-thousand-word window admitted and replayed as 40 chunks, data-led start snap (`WIN-START-SNAP`), 128-slot candidate ring | `[live]` |
| Clean DS on the beef draw lane after the full-window chunking (`DS-FAST2 ... ds_after=80000000`, c963) at the live-derived GS attribute map (maps=6), no SPH18; draw anchor after the first `0x3810` and raster enables emitted | `[live]` |
| Golden 2799-word MME pack on capture-less boots (`MME-GOLDEN overlay`, `MME-PRELUDE pack ir_words=2799`); `MME-CALL-HOLD -> MME-CARRY-SAVE -> MME-CARRY-FIRE -> MME-PACK-REARM -> MME-SA-REARM` fires; prelude latch kept across the per-fire channel recycle (`MME-LATCH-KEEP`); admitted-window chunks forwarded in order | `[live]` |
-| Guest draw submission: across 36 boots (c990-c1019) the client never submits a non-null `CALL(34)` draw macro — every `0x3910/0x3914` hit is an interior method write with `data=0x0`; no CALL header in the admitted windows (`DRAW-SCAN-PRE` found=0); guest EGL/dri2 failures and OOM kills in the same cycles; stores `wrote=0` / `0/1025` | `[wall]` |
+| Guest GL submission crossed (late 11-16): offscreen SDL EGL/GBM shim (`GZ_EGL`) gives GZDoom a real NVIDIA GL context without Xorg/DDX (`GL_RENDERER: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2`, `GL_VERSION: 4.6.0 NVIDIA 570.144`; no llvmpipe) | `[live]` |
+| Real GZDoom draw decoded and admitted: 12068 B window at push `0x402f9d8`, op=4 IMMD CALL to method `0x3800` (`imm=0xd48`) plus slots 44/57/58 (`0x3960/0x39c8/0x39d0`), no `0x3910/0x3914`; marker recognition, bind-free admission, draw-chunk-first, verbatim chunk replay (`3D chunk launch ... draw=1`) | `[live]` |
+| `CALL(0)` executes without trapping: immediate resolved as an IR address through client SA[0] then golden (`MME-CALL-RESOLVE`), not-resident calls elided (`MME-CALL-UNMAPPED ... reason=not-resident`); c1026/c1027 entered the captured macro (`macro-status=00000004`, mpc 0->4), first DS with real stage data (`DS-FAST2 ds_after=83044206 stage=015e0900,015e0a00,015c0400`); trap `0x80001528` decoded as a sticky TRAPPED_ADDR latch, not a cause/PC | `[live]` |
+| Per-draw MME macro body: never captured (the 59580-B prelude carries only the 12 setup macros, 573 code words pc 0..0x98; the draw push has no `0x114/0x11c`; `0xd48` is a length/argument, not an IR entry); the surviving wedge is the synthetic golden body (`badf1201 pc=513 mac=0xf1`) on a non-CALL(0) launch; stores `wrote=0`, no `px_nonblack` | `[wall]` |
| GZDoom video via the guest **software GL** path (Mesa llvmpipe): four byte-verified files (22 s flight + 18 s orbit, 640x480/1280x960, 30 fps) — a guaranteed-quality deliverable, **not** a vGPU rendering claim | `[live]` (software path) |
| Pack-completion and shallow-boot lotteries gate the deterministic release (throughput limiters) | `[wip]` |
| Window/screen present produces non-black screen pixels | `[wall]` |
@@ -172,18 +175,32 @@ start snap and a 128-slot candidate ring), the beef draw lane latches a
attribute map, capture-less boots get the **golden 2799-word MME pack** and
`MME-CALL-HOLD -> MME-CARRY-SAVE -> MME-CARRY-FIRE -> MME-PACK-REARM ->
MME-SA-REARM` fires, the prelude latch survives the per-fire channel recycle,
-and chunks are forwarded in order. The **decisive finding is guest-side**:
-across 36 boots (c990-c1019) the client never submits a non-null `CALL(34)`
-draw macro — every `0x3910/0x3914` hit is an interior method write with
-`data=0x0`, no CALL header exists in the admitted windows, and the same
-cycles logged guest EGL/dri2 failures and OOM kills. So the next work is
-guest-first: repair/verify the guest GL/EGL path and memory, capture one real
-frame submission, then the vertex/store and the window/screen present path
-(glxgears' window is black and a window draw can wedge X), with the per-boot
-X first-generation start lottery as the throughput limiter — then the first
-rendered screen frame. A GZDoom video was separately delivered through the
-guest's **software GL** path (Mesa llvmpipe) as a guaranteed-quality
-deliverable; it is not a vGPU rendering claim.
+and chunks are forwarded in order. The **late-11-16 wave crossed the guest submission gap.** An offscreen SDL
+EGL/GBM shim (`GZ_EGL`) gives GZDoom a real NVIDIA GL context without
+Xorg/DDX (`GL_RENDERER: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2`,
+`GL_VERSION: 4.6.0 NVIDIA 570.144`; no llvmpipe), and the real draw window
+surfaced: 12068 B at push `0x402f9d8`, an op=4 IMMD CALL to method `0x3800`
+(`imm=0xd48`) plus CALL slots 44/57/58 (`0x3960/0x39c8/0x39d0`), with no
+`0x3910/0x3914` and no colour-target bind of its own. Marker recognition now
+covers the real draw, admission happens on the marker even without a bind,
+the CALL-bearing chunk is forced first and every chunk is replayed verbatim.
+**`CALL(0)` no longer wedges**: eng89t resolves the immediate as an IR
+address through client SA[0] (then golden) and elides a not-resident call to
+a NOP; c1026/c1027 entered the captured macro (`macro-status=00000004`,
+`mpc` 0->4) without trapping, and c1027 produced the first DS with real
+stage data (`DS-FAST2 ds_after=83044206 stage=015e0900,015e0a00,015c0400`).
+The remaining gate is precise: the **client's per-draw MME macro body was
+never captured** (the 59580-byte prelude carries only the 12 setup macros;
+the draw push has no `0x114/0x11c`; `0xd48` is a length/argument), and the
+surviving wedge is the synthetic golden body (`badf1201 pc=513 mac=0xf1`).
+Next: capture the per-draw `0x114` upload or implement/verify the MME64 body,
+install it before the draw launch, then `DS-FAST2 ds_after=8[01]`,
+`GUEST-WIT va=0x15d`, `wrote>0`, `px0!=0`; then the window/screen present
+path (glxgears' window is black and a window draw can wedge X), with the
+per-boot X first-generation start lottery as the throughput limiter. A
+GZDoom video was separately delivered through the guest's **software GL**
+path (Mesa llvmpipe) as a guaranteed-quality deliverable; it is not a vGPU
+rendering claim.
## 6. What is not claimed
@@ -191,12 +208,15 @@ deliverable; it is not a vGPU rendering claim.
vGPU yet; every vGPU screen capture so far is black. The non-black frames
and the videos (45.4 s and 50 s) come from the off-screen pbuffer path
(pbuffer -> sysmem -> kvmfr ivshmem -> host reader), not from a windowed X
- screen capture. The host-side chain is proven end to end (admission, clean
- DS, golden pack, CALL hold, carry fire, SA re-arm), but the decisive 11-16
- finding is that the client did not submit a non-null `CALL(34)` draw macro
- in the recorded boots, so the stores are still missing; a synchronous
- window draw can wedge X, and X start retains a per-boot first-generation
- lottery. Those are the current walls.
+ screen capture. The host-side chain is proven end to end, and the late
+ 11-16 wave crossed the guest submission gap: the real NVIDIA EGL context,
+ the real op=4 `CALL(0)` `0x3800` draw admitted and replayed, `CALL(0)`
+ entering its captured macro without trapping, and the first DS with real
+ stage data. But the client's per-draw MME macro body was never captured,
+ the surviving wedge is the synthetic golden body, and no surface store or
+ pixel exists yet (`wrote=0`); a synchronous window draw can wedge X, and X
+ start retains a per-boot first-generation lottery. Those are the current
+ walls.
* **The 2026-11-16 GZDoom video is a software-GL deliverable, not a vGPU
result.** Mesa llvmpipe rendered it inside the guest; it is a
guaranteed-quality demonstration while the GPU-GL pixel path is being
diff --git a/wiki/Physical-GPU-Backend.md b/wiki/Physical-GPU-Backend.md
index cce054f..2e84df4 100644
--- a/wiki/Physical-GPU-Backend.md
+++ b/wiki/Physical-GPU-Backend.md
@@ -5,7 +5,7 @@
> guest-facing emulation. Canonical sources: [`../docs/03-architecture/08-physical-gpu-integration.md`](../docs/03-architecture/08-physical-gpu-integration.md)
> and [`../docs/03-architecture/11-physical-backend-guest-wiring.md`](../docs/03-architecture/11-physical-backend-guest-wiring.md); the docs tree wins on disagreement.
-Status: 2026-11-16, tree `master @ a06d4b13`. Tags: `[live]` proven with the
+Status: 2026-11-17, tree `master @ 1db3831e`. Tags: `[live]` proven with the
stock guest driver; `[gated]` implemented default-off; `[wip]` partially
built; `[wall]` current blocker; `[target]` planned end state.
@@ -109,7 +109,7 @@ FAIL a failed mutating operation parks the device in a locked fail-safe;
| Host RM client and first real engine work (static config, real objects, 4 KiB CE copy) | done `[live]` |
| Guest-copy forwarding, deferred release, hardware-primary copies, engine-authored relay, fault relay | verified live (seams parameterised and fail-open); the staged-transfer class is under repair `[live]` |
| CUDA kernel execution (`vectorAdd` and further clients) | done `[live]` — stock guest CUDA clients (vector-add, matrix-multiply, transformer) execute on the physical engine with verified results and engine-authored completions relayed to the guest |
-| Graphics method-stream execution (verbatim 3D replay, synthesized launches, direct-GL client channels) | `[wip]` — the engine retires real graphics streams, the display/KMS stack registers and X + stock GLX are green (the DDX/ScreenInit stability walls are closed, X green >10 minutes), captured GL sections execute, the direct-GL submission is fully decoded (macro-driven, no classic draw header), and the 11-16 wave proved the **host-side chain deterministic end to end**: the real frame pushes are admitted (persisted colour-target bind, draw markers inside counted runs, a 14.8-thousand-word window replayed as 40 chunks, a 128-slot candidate ring), the beef draw lane latches a clean DS (`DS-FAST2 ... ds_after=80000000`, c963) at the live-derived GS attribute map, a golden 2799-word MME pack serves capture-less boots, and `MME-CALL-HOLD -> MME-CARRY-FIRE -> MME-PACK-REARM -> MME-SA-REARM` fires with the latch kept across the channel recycle; the decisive finding is guest-side (36 boots, no non-null `CALL(34)` draw macro; guest EGL/dri2 failures and OOM kills), so the next work is a real guest draw submission, then the vertex/store and the window/screen present; a GZDoom video was separately delivered through the guest's software GL path (Mesa llvmpipe, not a vGPU claim) ([`Graphics-Execution.md`](Graphics-Execution.md)) |
+| Graphics method-stream execution (verbatim 3D replay, synthesized launches, direct-GL client channels) | `[wip]` — the engine retires real graphics streams, the display/KMS stack registers and X + stock GLX are green (the DDX/ScreenInit stability walls are closed, X green >10 minutes), captured GL sections execute, the direct-GL submission is fully decoded (macro-driven, no classic draw header), and the 11-16 wave proved the **host-side chain deterministic end to end**: the real frame pushes are admitted (persisted colour-target bind, draw markers inside counted runs, a 14.8-thousand-word window replayed as 40 chunks, a 128-slot candidate ring), the beef draw lane latches a clean DS (`DS-FAST2 ... ds_after=80000000`, c963) at the live-derived GS attribute map, a golden 2799-word MME pack serves capture-less boots, and `MME-CALL-HOLD -> MME-CARRY-FIRE -> MME-PACK-REARM -> MME-SA-REARM` fires with the latch kept across the channel recycle. The **late-11-16 wave crossed the guest submission gap**: an offscreen EGL/GBM shim gives GZDoom a real NVIDIA GL context without Xorg/DDX, the real op=4 `CALL(0)` `0x3800` draw (12068 B at push `0x402f9d8`) is admitted and replayed, `CALL(0)` executes its captured macro without trapping (eng89t), and c1027 reached the first DS with real stage data. The remaining gate is the client's per-draw MME macro body, never captured (the prelude carries only the 12 setup macros; the draw push has no `0x114/0x11c`), with the synthetic golden body the surviving wedge (`badf1201`); no surface store yet (`wrote=0`); a GZDoom video was separately delivered through the guest's software GL path (Mesa llvmpipe, not a vGPU claim) ([`Graphics-Execution.md`](Graphics-Execution.md)) |
## 7. The execution frontier
@@ -141,15 +141,19 @@ held window deterministically once the pack is resident (c772; the slot-34
census plus the SA[34] golden fill prove `client=golden=used=0x265`), so the 11-16 wave proved the **host-side chain deterministic end to end**
(admission of the real pushes, clean DS at the live-derived GS map, golden
2799-word pack, CALL hold, carry fire, SA re-arm, latch across the channel
-recycle); the **decisive finding is guest-side**: across 36 boots the client
-never submitted a non-null `CALL(34)` draw macro (interior `0x3910/0x3914`
-writes carry `data=0x0`; no CALL header in the admitted windows), and those
-cycles logged guest EGL/dri2 failures and OOM kills. The next work is
-guest-first (a real draw submission), then the vertex/store, the
-window/screen present, and the per-boot X first-generation start lottery
-before non-black window pixels. A GZDoom video was separately delivered
-through the guest's **software GL** path (Mesa llvmpipe) as a
-guaranteed-quality deliverable; it is not a vGPU rendering claim. The remaining
+recycle). The **late-11-16 wave crossed the guest submission gap**: a real
+NVIDIA EGL context without Xorg/DDX, the real op=4 `CALL(0)` `0x3800` draw
+admitted and replayed, `CALL(0)` executing its captured macro without
+trapping (the immediate resolves through client SA[0]/golden; not-resident
+calls are elided), and the first DS with real stage data. The remaining gate
+is the client's per-draw MME macro body, never captured (the prelude carries
+only the 12 setup macros; the draw push has no `0x114/0x11c`), with the
+synthetic golden body the surviving wedge (`badf1201`); then the vertex/store
+and the window/screen present, and the per-boot X first-generation start
+lottery before non-black window pixels. No surface store exists yet
+(`wrote=0`). A GZDoom video was separately delivered through the guest's
+**software GL** path (Mesa llvmpipe) as a guaranteed-quality deliverable; it
+is not a vGPU rendering claim. The remaining
compute work is the staged-transfer class (under repair), the every-boot
acceptance campaign, and per-guest execution isolation — see
[`Execution-Frontier.md`](Execution-Frontier.md) and
diff --git a/wiki/Project-Goals.md b/wiki/Project-Goals.md
index 40544ff..6d456b0 100644
--- a/wiki/Project-Goals.md
+++ b/wiki/Project-Goals.md
@@ -10,7 +10,7 @@
> [`Execution-Frontier.md`](Execution-Frontier.md) and
> [`Graphics-Execution.md`](Graphics-Execution.md).
-Status: 2026-11-16, tree `master @ a06d4b13`. Tags: `[live]` working with the
+Status: 2026-11-17, tree `master @ 1db3831e`. Tags: `[live]` working with the
stock guest driver; `[wip]` in progress; `[planned]` designed, not built;
`[target]` bring-up ahead; `[non-goal]` explicitly out of scope.
@@ -46,12 +46,12 @@ drivers, no license.**
## 3. Goals and their status
-| Goal | What success looks like | Status (2026-11-16) |
+| Goal | What success looks like | Status (2026-11-17) |
|---|---|---|
| Stock guest driver initialisation | The unmodified driver probes, initialises and enumerates as on bare metal (`nvidia-smi`) | `[live]` — TU104 reference platform |
| Full CUDA driver-API surface | Context creation, allocation, copies, free, destroy complete with correct results | `[live]` — the driver-API smoke prints `ALL OK`; the 64-byte payload round-trips |
| CUDA kernel execution on real hardware | Verified guest kernels execute on the physical GPU, with engine-authored completions waking the guest | `[live]` — vector-add, matrix-multiply and transformer clients green on fresh boots; the staged-transfer class, the every-boot acceptance campaign and per-guest isolation are in progress ([`Execution-Frontier.md`](Execution-Frontier.md)) |
-| OpenGL (3D graphics) | Stock guest GL applications render real pixels through the emulated vGPU | `[wip]` — the display/KMS stack and X run, the stock NVIDIA GLX path is fully green (`glxinfo -B` rc 0, OpenGL 4.6.0 direct, `glxgears` ~520 FPS), the 2D path is green, the DDX 3D replay executes, the X DDX/ScreenInit stability walls are closed (X green >10 minutes), captured GL sections execute on the engine, the direct-GL submission is fully decoded (macro-driven, no classic draw header), the released replay executes `DRAW_IAB` (`mac=0x22`, c788), the DS stage image is authored and live for both vertex slots, and the first non-black GPU-rendered frames plus captured videos (45.4 s and 50 s) are proven off-screen; GZDoom reaches `V_Init`. The 11-16 wave proved the **host-side chain deterministic end to end**: real frame pushes admitted (persisted colour-target bind, draw markers inside counted runs, 40-chunk full-window replay, 128-slot candidate ring), a clean DS on the draw lane (`DS-FAST2 ds_after=80000000`, c963) at the live-derived GS map, a golden 2799-word MME pack on capture-less boots, CALL hold/carry fire/SA re-arm with the latch kept across the channel recycle. The **decisive finding is guest-side**: across 36 boots the client never submitted a non-null `CALL(34)` draw macro (interior `0x3910/0x3914` writes carry `data=0x0`; no CALL header), and the same cycles logged guest EGL/dri2 failures and OOM kills. Window/screen pixels remain the frontier: a real guest draw submission first, then the vertex/store and the window/screen present, with the X first-generation start lottery as the throughput limiter. A GZDoom video was separately delivered through the guest's software GL path (Mesa llvmpipe) — not a vGPU rendering claim ([`OpenGL.md`](OpenGL.md)) |
+| OpenGL (3D graphics) | Stock guest GL applications render real pixels through the emulated vGPU | `[wip]` — the display/KMS stack and X run, the stock NVIDIA GLX path is fully green (`glxinfo -B` rc 0, OpenGL 4.6.0 direct, `glxgears` ~520 FPS), the 2D path is green, the DDX 3D replay executes, the X DDX/ScreenInit stability walls are closed (X green >10 minutes), captured GL sections execute on the engine, the direct-GL submission is fully decoded (macro-driven, no classic draw header), the released replay executes `DRAW_IAB` (`mac=0x22`, c788), the DS stage image is authored and live for both vertex slots, and the first non-black GPU-rendered frames plus captured videos (45.4 s and 50 s) are proven off-screen; GZDoom reaches `V_Init`. The 11-16 wave proved the **host-side chain deterministic end to end**: real frame pushes admitted (persisted colour-target bind, draw markers inside counted runs, 40-chunk full-window replay, 128-slot candidate ring), a clean DS on the draw lane (`DS-FAST2 ds_after=80000000`, c963) at the live-derived GS map, a golden 2799-word MME pack on capture-less boots, CALL hold/carry fire/SA re-arm with the latch kept across the channel recycle. The **late-11-16 wave crossed the guest submission gap**: an offscreen EGL/GBM shim gives GZDoom a real NVIDIA GL context without Xorg/DDX (`GL_RENDERER: NVIDIA GeForce RTX 2080 SUPER`, `GL_VERSION: 4.6.0 NVIDIA 570.144`; no llvmpipe), and the real op=4 `CALL(0)` `0x3800` draw (12068 B at push `0x402f9d8`, slots 44/57/58) is admitted, chunked and replayed; `CALL(0)` executes its captured macro without trapping (eng89t resolves the immediate through client SA[0]/golden and elides not-resident calls), and c1027 reached the first DS with real stage data. Window/screen pixels remain the frontier: the remaining gate is the client's per-draw MME macro body, never captured (the prelude carries only the 12 setup macros), with the synthetic golden body the surviving wedge; then the vertex/store and the window/screen present, with the X first-generation start lottery as the throughput limiter. A GZDoom video was separately delivered through the guest's software GL path (Mesa llvmpipe) — not a vGPU rendering claim ([`OpenGL.md`](OpenGL.md)) |
| Vulkan | Stock guest Vulkan applications render real pixels | `[wip]` — the pipeline runs end to end (device → command buffer → fence → readback); frames are black — program delivery and program-VA mapping are the frontier ([`Vulkan.md`](Vulkan.md)) |
| Windows guests (DirectX, CUDA) | A stock WDDM driver and stock D3D/CUDA applications run in Windows guests | `[target]` — not started; same emulation target ([`DirectX.md`](DirectX.md)) |
| Video (NVENC/NVDEC) | Encode/decode through the emulated device | `[planned]` |
diff --git a/wiki/Project-Plan.md b/wiki/Project-Plan.md
index 889ca87..9970e09 100644
--- a/wiki/Project-Plan.md
+++ b/wiki/Project-Plan.md
@@ -15,7 +15,7 @@
> [`../docs/06-portability/03-device-validation-and-porting-sequence.md`](../docs/06-portability/03-device-validation-and-porting-sequence.md);
> the docs tree wins on disagreement.
-Status: 2026-11-16, tree `master @ a06d4b13`. Tags: `[done]`, `[active]`,
+Status: 2026-11-17, tree `master @ 1db3831e`. Tags: `[done]`, `[active]`,
`[ahead]` — the plan's own state vocabulary, distinct from the goal tags.
## 1. How the plan works
@@ -40,11 +40,11 @@ itself:
## 2. The phases
-| Phase | What it delivers | Exit gate | State (2026-11-16) |
+| Phase | What it delivers | Exit gate | State (2026-11-17) |
|---|---|---|---|
| **P0 — Platform** | Emulated vGPU device, GSP boot and GSP-RM emulation, stock guest driver initialisation | Driver-API smoke green (`ALL OK`) = evaluation rung 2 | `[done]` |
| **P1 — First execution (compute)** | Guest CUDA kernels executing on the physical GPU, with engine-authored completions; then hardening | Verified clients + engine-authored completion = rung 3 core; hardening: staged-transfer class, every-boot acceptance, per-guest isolation | `[active]` — execution green; hardening in progress |
-| **P2 — Graphics execution** | OpenGL/Vulkan draw commands executed by the physical 3D pipeline and delivered as readable pixels | The graphics ladder: M-GL1 client context-init executes; M-GL2 `glxgears` non-black; M-GL3 GZDoom GL non-black through the mdev | `[active]` — between M-GL1 and M-GL2 with M-GL2's off-screen half proven: the display/KMS and DDX replay machinery work, X + stock GLX are green, the first non-black GPU-rendered frames and videos are captured, the X DDX/ScreenInit stability walls are closed, captured GL sections execute on the engine, the direct-GL submission is fully decoded (macro-driven, no classic draw header), the released replay executes `DRAW_IAB` (`mac=0x22`, c788), and the 11-16 wave proved the host-side chain deterministic end to end (real frame pushes admitted with a persisted colour-target bind, a 40-chunk full-window replay and a 128-slot ring; a clean DS `DS-FAST2 ds_after=80000000` at the live-derived GS map; a golden 2799-word MME pack; CALL hold/carry fire/SA re-arm with the latch kept across the channel recycle). The decisive finding is guest-side: across 36 boots the client never submitted a non-null `CALL(34)` draw macro, and the same cycles logged guest EGL/dri2 failures and OOM kills; the remaining walls are a real guest draw submission, the vertex/store, the window/screen present, and the per-boot X first-generation start lottery. A GZDoom video was separately delivered through the guest's software GL path (Mesa llvmpipe) — not a vGPU rendering claim |
+| **P2 — Graphics execution** | OpenGL/Vulkan draw commands executed by the physical 3D pipeline and delivered as readable pixels | The graphics ladder: M-GL1 client context-init executes; M-GL2 `glxgears` non-black; M-GL3 GZDoom GL non-black through the mdev | `[active]` — between M-GL1 and M-GL2 with M-GL2's off-screen half proven: the display/KMS and DDX replay machinery work, X + stock GLX are green, the first non-black GPU-rendered frames and videos are captured, the X DDX/ScreenInit stability walls are closed, captured GL sections execute on the engine, the direct-GL submission is fully decoded (macro-driven, no classic draw header), the released replay executes `DRAW_IAB` (`mac=0x22`, c788), and the 11-16 wave proved the host-side chain deterministic end to end (real frame pushes admitted with a persisted colour-target bind, a 40-chunk full-window replay and a 128-slot ring; a clean DS `DS-FAST2 ds_after=80000000` at the live-derived GS map; a golden 2799-word MME pack; CALL hold/carry fire/SA re-arm with the latch kept across the channel recycle). The late-11-16 wave crossed the guest submission gap: an offscreen EGL/GBM shim gives GZDoom a real NVIDIA GL context without Xorg/DDX, and the real op=4 `CALL(0)` `0x3800` draw (12068 B at push `0x402f9d8`) is admitted and replayed; `CALL(0)` executes its captured macro without trapping (eng89t), and c1027 reached the first DS with real stage data. The remaining walls are the client's per-draw MME macro body (never captured; the prelude carries only the 12 setup macros, and the synthetic golden body is the surviving wedge), the vertex/store, the window/screen present, and the per-boot X first-generation start lottery. A GZDoom video was separately delivered through the guest's software GL path (Mesa llvmpipe) — not a vGPU rendering claim |
| **P3 — Sustained and multi-tenant** | Frame rates without assistance; multiple VMs sharing the GPU with measured fairness; soak-stable operation | Graphics M-GL4 (60 fps, no forcing) and M-GL5 (two VMs, two mdevs); CUDA battery + soak; per-guest execution isolation = rungs 4/5 | `[ahead]` |
| **P4 — Breadth** | Video (NVENC/NVDEC), Windows/DirectX guests, live migration, non-KVM hypervisor transports | Per-case bring-up gates plus the matrix's evidence expectations | `[ahead]` |
| **P5 — Scale and portability** | New GPU generations and driver families carried forward; published performance programme | A profile + measured delta per version, validated on hardware; A/B numbers published per the measurement contract | `[ahead]` |
@@ -83,18 +83,22 @@ counted runs, a 14.8-thousand-word window replayed as 40 chunks, a 128-slot
candidate ring), a clean DS on the beef draw lane (`DS-FAST2
ds_after=80000000`, c963) at the live-derived GS map, a golden 2799-word MME
pack on capture-less boots, and CALL hold/carry fire/SA re-arm with the
-prelude latch kept across the channel recycle. The **decisive finding is
-guest-side**: across 36 boots (c990-c1019) the client never submitted a
-non-null `CALL(34)` draw macro — every `0x3910/0x3914` hit is an interior
-method write with `data=0x0`, no CALL header exists in the admitted windows,
-and the same cycles logged guest EGL/dri2 failures and OOM kills. The named
-walls are therefore a real guest draw submission first, then the
-vertex/store, the window/screen present path (glxgears' window is black and
-a window draw wedges X), and the per-boot X first-generation start lottery
-(even `modeNum` required; the dominant throughput limiter). A GZDoom video
-was separately delivered through the guest's **software GL** path (Mesa
-llvmpipe) as a guaranteed-quality deliverable; it is not a vGPU rendering
-claim.
+prelude latch kept across the channel recycle. The **late-11-16 wave crossed the
+guest submission gap**: an offscreen EGL/GBM shim gives GZDoom a real NVIDIA
+GL context without Xorg/DDX (`GL_RENDERER: NVIDIA GeForce RTX 2080
+SUPER/PCIe/SSE2`, `GL_VERSION: 4.6.0 NVIDIA 570.144`; no llvmpipe), and the
+real op=4 `CALL(0)` `0x3800` draw (12068 B at push `0x402f9d8`, slots
+44/57/58) is admitted and replayed; `CALL(0)` executes its captured macro
+without trapping (eng89t resolves the immediate through client SA[0]/golden
+and elides not-resident calls), and c1027 reached the first DS with real
+stage data. The named walls are therefore the client's per-draw MME macro
+body (never captured; the prelude carries only the 12 setup macros, and the
+synthetic golden body is the surviving wedge), then the vertex/store, the
+window/screen present path (glxgears' window is black and a window draw
+wedges X), and the per-boot X first-generation start lottery (even `modeNum`
+required; the dominant throughput limiter). A GZDoom video was separately
+delivered through the guest's **software GL** path (Mesa llvmpipe) as a
+guaranteed-quality deliverable; it is not a vGPU rendering claim.
Full detail:
[`Graphics-Execution.md`](Graphics-Execution.md) §6.
2. **Compute hardening (P1).** The staged-transfer class (failure modes proven,
diff --git a/wiki/Project-Status.md b/wiki/Project-Status.md
index ff067fa..c01439a 100644
--- a/wiki/Project-Status.md
+++ b/wiki/Project-Status.md
@@ -10,7 +10,7 @@
> (the execution frontier). When this page and the docs disagree, the docs tree
> wins.
-Status: 2026-11-16, tree `master @ a06d4b13`. Tags: `[live]` proven with the
+Status: 2026-11-17, tree `master @ 1db3831e`. Tags: `[live]` proven with the
stock guest driver; `[gated]` implemented, default-off or behind supervised
gates; `[wip]` partially implemented; `[wall]` current blocker; `[target]`
named success state; `[planned]` designed, not built.
@@ -28,7 +28,7 @@ named success state; `[planned]` designed, not built.
| Physical backend on real hardware (module-owned GPU running its real GSP-RM) | `[live]` boot, RPC session, object creation, copy-engine work and GR execution proven — the verified guest CUDA kernel clients execute through this backend, and graphics method streams execute on the engine ([`Graphics-Execution.md`](Graphics-Execution.md)) |
| Display and KMS on the emulated vGPU (nvidia-modeset/NvKms, `/dev/dri`, X) | `[live]` in the campaign configuration — the emulated display engine serves the guest's display push-buffer channels (notifier plus `UPDATE -> FINISHED`), nvidia-modeset/NvKms registers (`/dev/dri/card0`, `renderD128`, `fb0`), `nvidia-smi -L` enumerates and X settles. The X DDX idle-DMA/ScreenInit, USERD-latch lifetime, re-probe-thrash, Xorg kernel-mode-spin and flip-event walls were closed (X green for >10 minutes in a validated window); what remains is the per-boot **first-generation X start lottery**, which by 11-13/11-14 was the dominant throughput limiter for the graphics A/B runs (only an X started immediately after boot passes DDX DMA init; long stretches of dead starts, one green first-start boot). The display-capability seam is parameterised ([`Graphics-Execution.md`](Graphics-Execution.md)) |
| Multi-tenant isolation (mdev per VM, per-context page directories) | `[wip]` device-level coexistence works — multiple mediated devices with different emulated VRAM sizes and multiple guests coexist (two guests demonstrated); per-guest execution isolation for simultaneous CUDA guests is in progress |
-| OpenGL (3D graphics) | `[wip]` — the display/KMS stack registers, X and the stock NVIDIA GLX path are fully green (`glxinfo -B` returns 0 with OpenGL 4.6.0 and direct rendering; `glxgears` renders ~520 FPS with the emulated GPU's NVIDIA renderer), and the **first non-black GPU-rendered output** is proven: the pbuffer frame path produced 500/500 non-black 640x480 frames per run and captured videos (45.4 s on 2026-11-11; a 50 s 640x480 h264 capture on 2026-11-12). GZDoom reaches `V_Init: allocate screen` with its GL 4.6.0 context whenever the shared nvClip `modeNum` is even. **The direct-GL submission is now fully decoded:** no client push carries a method-grammar draw header — the channel's 9 NV906F entries tile one contiguous buffer and its per-frame work is carried as rewritten data-block blobs plus small state pushes (324/476/728 B) that invoke MME macros (the QMD-carrier hypothesis was tested and refuted). A content-gated FB-shadow rescue and a LOW-band rescue recover the recycled pushes: the client's draw-state push now opens a C597 section, is captured and marked for the verbatim 3D lane (the first direct-GL stream3d marks), and reaches the engine (`GR LAUNCH submitted`/`OK`, golden MME overlay accepted). **The MME chain now completes and executes the draw macro.** The multi-part keep-window mechanism won multi-frame windows; the part-launch poison was eliminated (the real fault was the client's own `SET_REPORT_SEMAPHORE`/`SET_NOTIFY` writes to client VAs that the host scratch page-table pool remaps — redirected to a mapped scratch slot; 49 cycles with zero poison and zero MMU faults); the 2799-word pack completes (2799/2799); engine-global completion plus keep-done-across-recycle produced the first `MME-PACK-REARM`; the fixed-CB region is aliased; and the released calls run macros through to **`DRAW_IAB` (`mac=0x22`)**. Two synthesized-prelude defects were then fixed: the SPH-BIND prelude self-destructed because an auto-dropped run broke its kept/final count (`444ae2c1`), and the stage block was silently skipped by a double-counted budget; with both fixed the prelude emits 84 words and the DS stage VAs populate (one validated boot carried the full post-REARM chain, `mac=0x22` and `DS 86040624`). **The DS stage-0/1 image is now authored and live**: a VTG SPH is written at `family+0x900` (`SPH-AUTHOR`, first word `020a0481`), the window's own later `0x2054` slot-1 bind is rewritten to the authored page (`SPH-SLOT1-REWRITE`), and the DS latch reads the authored image for both vertex slots (`DS-IMAGE st0=st1=020a0481 code=ff007321`; the DS value fell `0x86040626 -> 0x84000420`), reproduced on two boots. The 11-16 wave then proved the **host-side chain end to end**: the real frame pushes are admitted (a persisted colour-target bind carried from an earlier trusted push, draw markers accepted inside counted method runs, the 40-chunk full-window replay, a data-led window-start snap), the beef draw lane latches a **clean DS** (`DS-FAST2 ... ds_after=80000000`, c963, at the live-derived GS map), capture-less boots get the **golden 2799-word MME pack** (`MME-PRELUDE`, `MME-CARRY-FIRE`, `MME-PACK-REARM`, `MME-SA-REARM`), the prelude latch survives the per-fire channel recycle, and every admitted-window chunk is forwarded in order. The **decisive finding is guest-side**: across 36 boots (c990-c1019) the client never submitted a non-null `CALL(34)` draw macro — every `0x3910/0x3914` hit is an interior method write with `data=0x0`, no CALL header exists in the admitted windows, and the same cycles logged guest EGL/dri2 failures and OOM kills, so the guest GL path was not producing a real draw submission. A GZDoom video (4 files, 22 s flight + 18 s orbit, 640x480/1280x960, 30 fps, byte-verified) was delivered through the guest's **software GL** path (Mesa llvmpipe) as a guaranteed-quality deliverable; it is not a vGPU rendering claim. Window/screen pixels remain the frontier: a real guest draw submission first, then the vertex/store and the window/screen present, with the X first-generation start lottery as the throughput limiter ([`OpenGL.md`](OpenGL.md)) |
+| OpenGL (3D graphics) | `[wip]` — the display/KMS stack registers, X and the stock NVIDIA GLX path are fully green (`glxinfo -B` returns 0 with OpenGL 4.6.0 and direct rendering; `glxgears` renders ~520 FPS with the emulated GPU's NVIDIA renderer), and the **first non-black GPU-rendered output** is proven: the pbuffer frame path produced 500/500 non-black 640x480 frames per run and captured videos (45.4 s on 2026-11-11; a 50 s 640x480 h264 capture on 2026-11-12). GZDoom reaches `V_Init: allocate screen` with its GL 4.6.0 context whenever the shared nvClip `modeNum` is even. **The direct-GL submission is now fully decoded:** no client push carries a method-grammar draw header — the channel's 9 NV906F entries tile one contiguous buffer and its per-frame work is carried as rewritten data-block blobs plus small state pushes (324/476/728 B) that invoke MME macros (the QMD-carrier hypothesis was tested and refuted). A content-gated FB-shadow rescue and a LOW-band rescue recover the recycled pushes: the client's draw-state push now opens a C597 section, is captured and marked for the verbatim 3D lane (the first direct-GL stream3d marks), and reaches the engine (`GR LAUNCH submitted`/`OK`, golden MME overlay accepted). **The MME chain now completes and executes the draw macro.** The multi-part keep-window mechanism won multi-frame windows; the part-launch poison was eliminated (the real fault was the client's own `SET_REPORT_SEMAPHORE`/`SET_NOTIFY` writes to client VAs that the host scratch page-table pool remaps — redirected to a mapped scratch slot; 49 cycles with zero poison and zero MMU faults); the 2799-word pack completes (2799/2799); engine-global completion plus keep-done-across-recycle produced the first `MME-PACK-REARM`; the fixed-CB region is aliased; and the released calls run macros through to **`DRAW_IAB` (`mac=0x22`)**. Two synthesized-prelude defects were then fixed: the SPH-BIND prelude self-destructed because an auto-dropped run broke its kept/final count (`444ae2c1`), and the stage block was silently skipped by a double-counted budget; with both fixed the prelude emits 84 words and the DS stage VAs populate (one validated boot carried the full post-REARM chain, `mac=0x22` and `DS 86040624`). **The DS stage-0/1 image is now authored and live**: a VTG SPH is written at `family+0x900` (`SPH-AUTHOR`, first word `020a0481`), the window's own later `0x2054` slot-1 bind is rewritten to the authored page (`SPH-SLOT1-REWRITE`), and the DS latch reads the authored image for both vertex slots (`DS-IMAGE st0=st1=020a0481 code=ff007321`; the DS value fell `0x86040626 -> 0x84000420`), reproduced on two boots. The 11-16 wave then proved the **host-side chain end to end**: the real frame pushes are admitted (a persisted colour-target bind carried from an earlier trusted push, draw markers accepted inside counted method runs, the 40-chunk full-window replay, a data-led window-start snap), the beef draw lane latches a **clean DS** (`DS-FAST2 ... ds_after=80000000`, c963, at the live-derived GS map), capture-less boots get the **golden 2799-word MME pack** (`MME-PRELUDE`, `MME-CARRY-FIRE`, `MME-PACK-REARM`, `MME-SA-REARM`), the prelude latch survives the per-fire channel recycle, and every admitted-window chunk is forwarded in order. At that point the decisive finding was guest-side: across 36 boots (c990-c1019) the client never submitted a non-null `CALL(34)` draw macro — every `0x3910/0x3914` hit is an interior method write with `data=0x0`, no CALL header exists in the admitted windows, and the same cycles logged guest EGL/dri2 failures and OOM kills, so the guest GL path was not producing a real draw submission. A GZDoom video (4 files, 22 s flight + 18 s orbit, 640x480/1280x960, 30 fps, byte-verified) was delivered through the guest's **software GL** path (Mesa llvmpipe) as a guaranteed-quality deliverable; it is not a vGPU rendering claim. The **late-11-16 wave then crossed the guest submission gap**: an offscreen SDL EGL/GBM shim gives GZDoom a real NVIDIA GL context without Xorg/DDX (`GL_RENDERER: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2`, `GL_VERSION: 4.6.0 NVIDIA 570.144`; no llvmpipe), and the real 12068-B draw window (op=4 `CALL(0)` method `0x3800`, imm `0xd48`, plus slots 44/57/58) is admitted, chunked and replayed verbatim. `CALL(0)` no longer wedges: eng89t resolves the immediate through client SA[0] (then golden) and elides a not-resident call to a NOP; c1026/c1027 entered the captured macro without trapping and c1027 produced the first DS with real stage data. The remaining gate is precise: the client's **per-draw MME macro body was never captured** (the prelude carries only the 12 setup macros), and the surviving wedge is the synthetic golden body (`badf1201`); stores on the vGPU path still miss (`wrote=0`, no `px_nonblack`). Next: capture/verify the per-draw macro body, then the vertex/store and the window/screen present, with the X first-generation start lottery as the throughput limiter ([`OpenGL.md`](OpenGL.md)) |
| Vulkan (3D/compute) | `[wip]` — the guest Vulkan pipeline runs end to end on the emulated vGPU (device, allocation, pipeline, command buffer, fence, queue submit, readback) and the engine executes translated launches; frames are still black — program delivery and program-VA mapping are the frontier ([`Vulkan.md`](Vulkan.md)) |
| DirectX / Windows guests | `[planned]` (target) — no Windows guest booted yet; the architecture is the same emulation target ([`DirectX.md`](DirectX.md)) |
| Video (NVENC/NVDEC) | `[planned]` |
@@ -83,15 +83,18 @@ GZDoom reaches its screen-allocation stage with GL 4.6.0 on an even modeNum.
The host-side draw chain is now proven end to end — admission of the real
frame pushes, a clean DS (`DS-FAST2 ds_after=80000000` on the draw lane), the
golden 2799-word MME pack, the CALL hold, the release carrier and the SA
-re-arm all fire — and the decisive finding of the 11-16 wave is guest-side:
-in 36 boots the client never submitted a non-null `CALL(34)` draw macro
-(every `0x3910/0x3914` hit is an interior method write with `data=0x0`), and
-the guest's GL path logged EGL/dri2 failures and OOM kills in that boot
-class. A GZDoom video was delivered through the guest's *software* GL path
-(Mesa llvmpipe) as a guaranteed-quality deliverable; it is not a vGPU
-rendering claim. Windowed/screen pixels remain the frontier (a real guest
-draw submission, then the vertex/store and the window/screen present, with X
-start keeping a first-generation lottery) — see [`OpenGL.md`](OpenGL.md). The
+re-arm all fire — and the late-11-16 wave crossed the guest submission gap:
+an offscreen EGL/GBM shim gives GZDoom a real NVIDIA GL context without
+Xorg/DDX, and the real `CALL(0)` `0x3800` draw is admitted, chunked and
+replayed, executes its captured macro without trapping, and reaches a DS
+with real stage data. The remaining gate is the client's per-draw MME macro
+body (never captured; the prelude carries only the setup macros), with the
+synthetic golden body the surviving wedge and no surface store yet. A GZDoom
+video was delivered through the guest's *software* GL path (Mesa llvmpipe)
+as a guaranteed-quality deliverable; it is not a vGPU rendering claim.
+Windowed/screen pixels remain the frontier (the per-draw macro body, then
+the vertex/store and the window/screen present, with X start keeping a
+first-generation lottery) — see [`OpenGL.md`](OpenGL.md). The
risc-v-gsp-rm-debugger workbench
([`Riscv-GSP-RM-Debugger.md`](Riscv-GSP-RM-Debugger.md)) is the host-side
tooling used to study the firmware side of that frontier.
diff --git a/wiki/System-Overview.md b/wiki/System-Overview.md
index 65aecbe..771511e 100644
--- a/wiki/System-Overview.md
+++ b/wiki/System-Overview.md
@@ -7,7 +7,7 @@
> and [`../docs/03-architecture/10-interaction-and-scheduling.md`](../docs/03-architecture/10-interaction-and-scheduling.md)
> for the full picture); the docs tree wins on disagreement.
-Status: 2026-11-16, tree `master @ a06d4b13`. Tags: `[live]` proven with the
+Status: 2026-11-17, tree `master @ 1db3831e`. Tags: `[live]` proven with the
stock guest driver; `[gated]` implemented default-off; `[wip]` partial;
`[wall]` current blocker; `[target]` designed end state.
@@ -160,12 +160,16 @@ RPC from the guest to "firmware":
ds_after=80000000`, c963) at the live-derived GS attribute map,
capture-less boots get a **golden 2799-word MME pack**, and
`MME-CALL-HOLD -> MME-CARRY-FIRE -> MME-PACK-REARM -> MME-SA-REARM` fires
- with the prelude latch kept across the channel recycle. The **decisive
- finding is guest-side**: across 36 boots (c990-c1019) the client never
- submitted a non-null `CALL(34)` draw macro (interior `0x3910/0x3914`
- writes carry `data=0x0`; no CALL header in the admitted windows), and the
- same cycles logged guest EGL/dri2 failures and OOM kills. The remaining
- gates are a real guest draw submission, then the vertex/store and the
+ with the prelude latch kept across the channel recycle. The **late-11-16
+ wave crossed the guest submission gap**: an offscreen EGL/GBM shim gives
+ GZDoom a real NVIDIA GL context without Xorg/DDX, the real op=4
+ `CALL(0)` `0x3800` draw (12068 B at push `0x402f9d8`) is admitted and
+ replayed, `CALL(0)` executes its captured macro without trapping (eng89t
+ resolves the immediate through client SA[0]/golden and elides
+ not-resident calls), and c1027 reached the first DS with real stage data.
+ The remaining gates are the client's per-draw MME macro body (never
+ captured; the prelude carries only the 12 setup macros, and the synthetic
+ golden body is the surviving wedge), then the vertex/store and the
window/screen present; the per-boot X first-generation start lottery is
the dominant throughput limiter. A GZDoom video was separately delivered
through the guest's **software GL** path (Mesa llvmpipe) as a