summaryrefslogtreecommitdiffstats
path: root/wiki/Physical-GPU-Backend.md
diff options
context:
space:
mode:
Diffstat (limited to 'wiki/Physical-GPU-Backend.md')
-rw-r--r--wiki/Physical-GPU-Backend.md23
1 files changed, 14 insertions, 9 deletions
diff --git a/wiki/Physical-GPU-Backend.md b/wiki/Physical-GPU-Backend.md
index 9d22979..cce054f 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-15, tree `master @ 88d5005a`. Tags: `[live]` proven with the
+Status: 2026-11-16, tree `master @ a06d4b13`. 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), the client's draw-state push reaches the engine, the MME pack completes, the released replay executes `DRAW_IAB` (`mac=0x22`, c788; TCS-off DS clean, synthetic viewport, chained release), the DS stage image is authored and live for both vertex slots (`st0=st1=020a0481`), the saved-window release carrier replays the held window deterministically once the pack is resident, and the first non-black GPU-rendered frames are captured off-screen; the remaining vertex-buffer identity, the render-target store/alias visibility, the pack-completion lottery and the window/screen present are the frontier ([`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 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)) |
## 7. The execution frontier
@@ -138,13 +138,18 @@ vertices), the DS stage image is authored and
live for both vertex slots (`st0=st1=020a0481`; DS `0x86040626 ->
0x84000420`, two boots), and the saved-window release carrier replays the
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
-remaining graphics gates are the vertex-buffer identity (no captured client
-push binds the stream; the eng71 scan candidate is a heuristic), the
-render-target store/alias visibility (the big-surface alias pages do not yet
-enter `GUEST-WIT`), the pack-completion lottery,
-the stores, the window/screen present, and the per-boot binding/X
-first-generation start lottery before non-black window pixels. The remaining
+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
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