summaryrefslogtreecommitdiffstats
path: root/wiki/Execution-Frontier.md
diff options
context:
space:
mode:
Diffstat (limited to 'wiki/Execution-Frontier.md')
-rw-r--r--wiki/Execution-Frontier.md87
1 files changed, 45 insertions, 42 deletions
diff --git a/wiki/Execution-Frontier.md b/wiki/Execution-Frontier.md
index 4549f08..bfecad9 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-15, tree `master @ 88d5005a`.
+Status: 2026-11-16, tree `master @ a06d4b13`.
Tags: `[live]` observed; `[wip]` partial; `[wall]` current blocker; theories
are labelled as such.
@@ -131,24 +131,32 @@ fire -> synthetic `GR LAUNCH 0x6d6d6500` -> `MME-PACK-REARM` -> DS
`0x84000420`), and the held-CALL census plus the SA[34] golden fill prove the
`DRAW_IAB` call and its target are present (`MME-CALL-TARGET slot=34
method=0x3910 client=0x265 golden=0x265 used=0x265`). What is missing is
-**window/screen pixels through the NVIDIA path**: **the draw macro now
-executes end to end** — c788 ran `DRAW_IAB` (`mac=0x22`) on a released held
-window after the `MME-DRAW-MOVE` reorder, TCS-off (`45dbcdcd`) clears the DS
-latch (the `0x84000420` was the synthesized TCS bind), a synthetic full-RT
-viewport (`dab4a02c`) and a release chained after any GR launch
-(`3481e62d`) complete the replay, and the DRAW_IAB body decodes with the
-public Mesa MME toolchain (`mme_tu104_sim`: slot 34, 8 draws of 3 vertices)
-— but the **vertex buffer** is not identified (no captured client push binds
-the stream directly; the eng71 scan's CB-page candidate is a heuristic, and
-a stale nonzero `VS0` also stores nothing) and **render-target store
-visibility** is unproven (the release writes only CB/GR-context/report
-pages; the big-surface alias pages do not yet populate `GUEST-WIT`); eng74
-(`88d5005a`) dumps the scanned vertex candidate (`VS-BLOB`) and records the
-alias RT pages in the WIT, so both blockers are measurable next boot. The
-draw does not store (`wrote=0`, `0/1025`, `px0=0`); the window/screen
-present path is unproven, glxgears' window is black, and a synchronous window
-draw wedges X on some boots. The per-boot binding and X first-generation
-start lottery are now the dominant throughput limiter. The guest Vulkan
+**window/screen pixels through the NVIDIA path**. The draw macro executes end
+to end (c788 ran `DRAW_IAB` (`mac=0x22`) on a released held window after the
+`MME-DRAW-MOVE` reorder; TCS-off, `45dbcdcd`, clears the DS latch; a synthetic
+full-RT viewport, `dab4a02c`, and a chained release, `3481e62d`, complete the
+replay; the body decodes with the public Mesa MME toolchain as 8 draws of 3
+vertices), 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,
+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
pipeline's inline-to-memory upload arm is its gap. The full picture lives on
[`Graphics-Execution.md`](Graphics-Execution.md).
@@ -215,29 +223,24 @@ GPU-rendered frames and videos are captured off-screen, and the direct-GL
ring/USERD machinery is substantially hardened); the direct-GL submission is
fully decoded (macro-driven; no method-grammar draw header in any push), the
recycled pushes are recovered, and the client's draw-state push opens,
-captures and reaches the engine. The MME chain now completes and executes the
-draw macro: multi-frame keep-windows land, the 2799-word pack completes, the
-first `MME-PACK-REARM` fires, the fixed-CB region is aliased, and `DRAW_IAB`
-(`mac=0x22`) runs with the SPH-BIND prelude intact and the DS stage VAs
-populated. The **DS stage-0/1 image is now authored and live** (a VTG SPH at
-`family+0x900`, fetched by both vertex slots as `st0=st1=020a0481`; DS fell
-`0x86040626 -> 0x84000420`, reproduced on two boots). The release is
-host-deterministic when the pack completes: the saved-window release carrier
-re-submits the held window with the calls released (c772), and the held-CALL
-census plus SA[34] golden fill prove the slot-34 `DRAW_IAB` address
-(`client=golden=used=0x265`). The draw macro now executes end to end (c788 ran
-`DRAW_IAB` `mac=0x22` on the released held window after the `MME-DRAW-MOVE`
-reorder; TCS-off clears the DS latch; the synthetic viewport and the chained
-release complete the replay; the body decodes with the public Mesa MME
-toolchain as 8 draws of 3 vertices). The remaining blockers are the vertex
-buffer (no captured client push binds the stream directly; the eng71 scan
-candidate is a heuristic) and render-target store/alias visibility (the
-big-surface alias pages do not yet enter `GUEST-WIT`; eng74 `88d5005a`
-records them and dumps the candidate blob), so the draws still do
-not store.
-glxgears' window is black, a window draw wedges X on some
-boots, and the per-boot binding plus X first-generation start lottery is the
-dominant throughput limiter
+captures and reaches the engine. The 11-16 wave then proved the **host-side draw chain deterministic end to
+end**: the real frame pushes are admitted (a persisted colour-target bind
+from an earlier trusted push, draw markers inside counted method runs, the
+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, 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
([`Graphics-Execution.md`](Graphics-Execution.md)).
## 6. Lines of investigation (live)