diff options
Diffstat (limited to 'wiki/Execution-Plane.md')
| -rw-r--r-- | wiki/Execution-Plane.md | 32 |
1 files changed, 18 insertions, 14 deletions
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 |
