From 6107a002a5fb532f0b673c107c4cbe5d0d8925b4 Mon Sep 17 00:00:00 2001 From: Arthur Hanson Rasmusson Date: Mon, 16 Nov 2026 22:55:55 -0500 Subject: docs(wiki): 2026-11-16 evening status refresh - host draw chain proven end to end, guest submission is the wall - 11 wiki pages refreshed: the real frame pushes are admitted (persisted colour-target bind, draw markers inside counted runs, 40-chunk full-window replay, 128-slot ring); the beef draw lane latches a clean DS at the live-derived GS map; capture-less boots get the golden 2799-word MME pack; CALL hold/carry fire/SA re-arm fire with the latch kept across the channel recycle. - Decisive finding recorded as guest-side: 36 boots (c990-c1019) show no non-null CALL(34) draw macro from the client (interior 0x3910/0x3914 writes carry data=0x0) plus guest EGL/dri2 failures and OOM kills. - GZDoom video delivered via the guest software GL path (Mesa llvmpipe) is documented as a non-vGPU deliverable. - STATE-CURRENT.md snapshot prepended; wiki published to open-iov.org (revs 24210-24220; 68 pages audited, 0 problems). --- wiki/Graphics-Execution.md | 157 +++++++++++++++++++++++---------------------- 1 file changed, 82 insertions(+), 75 deletions(-) (limited to 'wiki/Graphics-Execution.md') diff --git a/wiki/Graphics-Execution.md b/wiki/Graphics-Execution.md index 34b8147..4d879df 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-15, tree `master @ 88d5005a`. Tags: `[live]` observed end to +Status: 2026-11-16, tree `master @ a06d4b13`. Tags: `[live]` observed end to end; `[wip]` partially built; `[wall]` current blocker; `[target]` defined success state; `[planned]` designed, not built. @@ -147,19 +147,33 @@ fidelity: toolchain (`mme_tu104_sim`): slot 34 (`0x265`) emits 8 draws of 3 vertices (`SET_VERTEX_ARRAY_START` 0..21, `DRAW_VERTEX_ARRAY` 3). A synthetic full-RT viewport (`dab4a02c`) and a release chained after any GR launch - (`3481e62d`) complete the replay. **The remaining blockers are the vertex - buffer and render-target visibility**: no captured client push binds the - vertex stream directly (no `0x1c00/0x1c04` pair outside SPH payloads), so - the `VS0` bound by the eng71 scan (`sema_gl_vs_autobind`) is a heuristic - CB-page candidate (score 8), and a nonzero stale `VS0` also stores nothing - (c811); and the release writes only CB/GR-context/report pages — the - big-surface alias pages did not populate `GUEST-WIT`, so an RT store would - be invisible. eng74 (`88d5005a`) now dumps the scanned candidate blob - (`VS-BLOB`) and records the surface-alias RT pages in the WIT, so both - blockers are measurable on the next boot. Stores 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 are the throughput limiters. + (`3481e62d`) complete the replay. **The 11-16 wave then proved the host-side chain end to end.** The real + frame pushes are admitted: the colour-target bind is persisted from an + earlier trusted push (`RT-PERSIST`; the client binds the target once, not + per frame), draw markers are accepted inside counted method runs, and the + 14.8-thousand-word window is admitted and replayed as 40 chunks with a + data-led start snap (`WIN-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 (maps=6), with no SPH18; the + draw anchor now moves the call after the first `0x3810` vertex-stream run + and the raster enables are emitted. Capture-less boots get a **golden + 2799-word MME pack** built from the golden library (`MME-GOLDEN`, + `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. ## 4. The channel and object picture * **Every submission lives on a channel**: a GPFIFO ring plus engine objects, @@ -219,9 +233,12 @@ swaps, and the GR backend no longer times out (the pair-close/pair-safe DDX/ScreenInit stability walls are closed, and the direct-GL ring/USERD machinery is hardened. The MME pack completes and the draw macro runs, and the authored DS stage image is live for both vertex slots; the released - replay now executes the `DRAW_IAB` (`mac=0x22`) with a synthetic viewport, - and the next step is the vertex-buffer identity and the render-target - store/alias visibility, then the window/screen present path. + 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. 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 @@ -230,53 +247,34 @@ requires it switched off, along with any external poke. ## 6. Where the frontier is (ranked walls) -1. **Direct-GL MME draw-macro execution and stores** `[wall]`. Delivery to - the lane and the multi-part program gate are closed: the submission is - fully decoded (nine NV906F entries tile one contiguous buffer; no - method-grammar draw header exists; the per-frame work is data-block blobs - plus real state pushes that invoke MME macros), the recycled pushes are - recovered by the content-gated FB-shadow and LOW-band rescues, the - client's 324-B draw-state push opens a `C597` section, is captured and - marked for the verbatim 3D lane, and reaches the engine with the golden - MME overlay (`GR LAUNCH submitted` + OK). The 2799-word pack completes - (2799/2799), the first `MME-PACK-REARM` fires (engine-global completion - plus keep-done-across-recycle), the fixed-CB region is aliased, the - released calls run macros, and `DRAW_IAB` (`mac=0x22`) executes on the 324-B - window class after a cross-lane `MME-PACK-REARM`. The **DS stage-0/1 image - is now authored and live**: a VTG SPH is written at `family+0x900` - (`SPH-AUTHOR`, first word `020a0481`) and the window's own `0x2054` slot-1 - bind is rewritten to it (`SPH-SLOT1-REWRITE`), so the DS latch reads - `st0=st1=020a0481 code=ff007321` and the DS value falls - `0x86040626 -> 0x84000420` (reproduced on two boots). The release is - host-deterministic when the pack completes: the saved-window release - carrier snapshots the held window and re-submits it with calls released - once the pack is resident (c772: `MME-CARRY-SAVE win=240 held=68` -> - `MME-CARRY-FIRE mode=release` -> synthetic `GR LAUNCH push=0x6d6d6500` -> - `MME-PACK-REARM` gen=5 -> DS `0x84000420` -> `MME-CARRY-COMPLETE`); the - held-CALL census and SA[34] golden fill settle the call and its address - (`MME-CALL-TARGET slot=34 method=0x3910 client=0x265 golden=0x265 - used=0x265`; `MME-GOLDEN sa-fill slot=34 entry=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 (`MME-FAST ... mac=0x22 - run=1`), TCS-off (`45dbcdcd`) clears the DS latch, the synthetic viewport - (`dab4a02c`) and the chained release (`3481e62d`) complete the replay, and - the body decodes with the public Mesa MME toolchain (`mme_tu104_sim`: 8 - draws of 3 vertices). **The remaining blockers are the vertex buffer and - render-target visibility**: no captured client push binds the vertex - stream directly (the eng71 scan lands a heuristic CB-page candidate, - score 8; a stale nonzero `VS0` also stores nothing), and the - big-surface alias pages do not enter `GUEST-WIT`, so an RT store would be - invisible; eng74 (`88d5005a`) dumps the scanned candidate (`VS-BLOB`) and - records the alias RT pages in the WIT for the next boot; the release - writes only CB/GR-context/report pages and stores - still miss (`wrote=0`, `0/1025`, `px0=0`). Closed on the way: the QMD-carrier theory - (refuted: no QMD bit in the entry format, no QMD magic in 256 MiB BAR1) - and RT routing (the clear targets RT0 while the window binds RT1; RT0 bind - verified 16x with correct target/geometry, still 61/61 `wrote=0`). The - `CODESRC` fault-park class is prevented by relocating a suspect program - page 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`). +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`). 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 @@ -344,8 +342,11 @@ requires it switched off, along with any external poke. | DS stage-0/1 image: a VTG SPH is authored at `family+0x900` and the window's own slot-1 bind rewritten to it; the DS latch reads `st0=st1=020a0481` | `[live]` | | Saved-window release carrier (held window snapshotted at `MME-CALL-HOLD` and re-submitted with calls released once the pack is resident, c772); held-CALL census + SA[34] golden fill (`client=golden=used=0x265`); synthetic full-RT viewport (`dab4a02c`); release chained after any GR launch (`3481e62d`) | `[live]` | | Per-stage SPH disable (TCS off, `45dbcdcd`) clears the DS latch (the `0x84000420` was the synthesized TCS bind) | `[live]` | -| Vertex buffer: the client's captured pushes never bind the stream directly (no `0x1c00/0x1c04` pair outside SPH payloads); the eng71 scan binds a heuristic CB-page candidate (score 8); a stale nonzero `VS0` also stores nothing (c811); eng74 `VS-BLOB` dumps the candidate for validation/rejection | `[wall]` | -| Render-target store/alias visibility: the release writes only CB/GR-context/report pages; eng74 (`88d5005a`) records the surface-alias RT pages in `GUEST-WIT` so an alias store is provable; stores `wrote=0` / `0/1025` | `[wall]` | +| 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]` | +| 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]` | | X screen-init first-generation lottery (`modeNum` parity; only an immediately-post-boot X passes DDX DMA init; dominant throughput limiter) | `[wip]` | @@ -355,18 +356,24 @@ requires it switched off, along with any external poke. ## 8. What is not claimed * No **window/screen** pixel has been produced by the emulated vGPU's 3D - pipeline yet; every screen capture so far is black. The proven 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. + pipeline yet; every vGPU screen capture so far is black. The proven + 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 2026-11-16 GZDoom video is a software-GL deliverable, not a vGPU + result.** It was rendered by Mesa llvmpipe inside the guest + (`GL_RENDERER: llvmpipe`) and captured through the same SDL hook; it exists + as a guaranteed-quality demonstration while the GPU-GL pixel path is being + worked. It must not be read as the emulated vGPU's 3D pipeline rendering + 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 client's draw-state push reaches the engine, the MME - program completes and the released replay executes the draw macro - (`DRAW_IAB`, `mac=0x22`, with a synthetic viewport), but the draw's vertex - buffer is not yet identified and the render-target alias pages are not yet - WIT-visible, so the stores are still missing and the window stays black. + 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. * 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 -- cgit v1.2.3