diff options
Diffstat (limited to 'wiki/OpenGL.md')
| -rw-r--r-- | wiki/OpenGL.md | 63 |
1 files changed, 40 insertions, 23 deletions
diff --git a/wiki/OpenGL.md b/wiki/OpenGL.md index 4453c96..62f9a01 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-15, tree `master @ 88d5005a`. Tags: `[live]` observed with the +Status: 2026-11-16, tree `master @ a06d4b13`. Tags: `[live]` observed with the stock guest driver; `[wip]` partial; `[wall]` current blocker; `[target]` defined success state. @@ -106,8 +106,11 @@ Rated honestly, against the milestone ladder in the plan: | 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, 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 screen pixels | `[wall]` | | X screen-init first-generation lottery (`modeNum` parity; only an immediately-post-boot X passes DDX DMA init; dominant throughput limiter) | `[wip]` | @@ -160,30 +163,44 @@ 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). -The remaining blockers are the **vertex buffer** (no captured client push -binds the stream directly; the eng71 scan's CB-page candidate is a heuristic, -score 8; a stale nonzero `VS0` also stores nothing (c811)) and -**render-target visibility** (the release writes only CB/GR-context/report -pages, and the big-surface alias pages do not yet populate `GUEST-WIT`), so -the stores still miss; eng74 (`88d5005a`) dumps the scanned candidate -(`VS-BLOB`) and records the alias RT pages in the WIT for the next boot; -then the window/screen present path (glxgears' window -is black and a window draw can wedge X), and the per-boot binding/X -first-generation start lottery — then the first rendered screen frame. +The 11-16 wave then proved the **host-side chain end to end**: 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 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. ## 6. What is not claimed * No **window/screen** frame has rendered real pixels through the emulated - vGPU yet; every 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 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; a synchronous window draw can wedge X, and - X start retains a per-boot first-generation lottery. Those are the current - walls. + 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. +* **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 + worked, not evidence of the emulated vGPU's 3D pipeline. * GZDoom reaching `V_Init: allocate screen` is not a rendered-frame claim; it proves the client's GL init and the direct-GL GR lane, not the game loop or a presented frame. |
