From dc54de9ef4f1c27ad51f352a08e2c98b0c64cd64 Mon Sep 17 00:00:00 2001 From: Arthur Hanson Rasmusson Date: Mon, 16 Nov 2026 00:40:05 -0500 Subject: docs(wiki): 2026-11-16 status refresh - DRAW_IAB mac=0x22 executes end to end (c788); TCS-off DS clean; remaining blockers are the vertex buffer (eng74 VS-BLOB) and render-target store/alias visibility (eng74 alias WIT); stores still 0 --- STATE-CURRENT.md | 61 ++++++++++++++++++++++++ wiki/.publish-manifest.json | 110 +++++++++++++++++++++---------------------- wiki/Execution-Frontier.md | 61 +++++++++++++----------- wiki/Execution-Plane.md | 19 +++++--- wiki/FAQ.md | 19 ++++---- wiki/Graphics-Execution.md | 96 ++++++++++++++++++++----------------- wiki/Host-Module.md | 17 ++++--- wiki/OpenGL.md | 58 ++++++++++++----------- wiki/Physical-GPU-Backend.md | 16 +++++-- wiki/Project-Goals.md | 4 +- wiki/Project-Plan.md | 26 ++++++---- wiki/Project-Status.md | 16 +++---- wiki/System-Overview.md | 29 +++++++----- 13 files changed, 322 insertions(+), 210 deletions(-) diff --git a/STATE-CURRENT.md b/STATE-CURRENT.md index 0414c56..f1d8313 100644 --- a/STATE-CURRENT.md +++ b/STATE-CURRENT.md @@ -1,5 +1,66 @@ # Open-IOV Current State +> **Snapshot: 2026-11-16 ~00:35 (SESSION 157 continued; HEAD `88d5005a` == +> `vgpu/master`; working tree clean; supersedes the 2026-11-15 ~16:35 entry +> below).** +> The graphics front crossed a second major gate since the last snapshot: +> **the `DRAW_IAB` macro now executes end to end**, and the remaining wall is +> the **store** (the draw's vertex buffer and render-target visibility). +> +> - c788 (module `6aeb20c7`) is the milestone: the chained saved-window +> release fired (`MME-CARRY-FIRE mode=release held=68 win=240 push=0x6d6d6500`) +> -> `MME-PACK-REARM gen=5` -> `MME-SA-REARM 7 slot(s)` -> +> `MME-DRAW-PLAN slot=34 src_off=0x334 dst_off=0x204 span=14` -> +> `MME-DRAW-MOVE` -> `MME-FAST ... macro-status=00122266(mpc=614 mac=0x22 +> run=1)` — the draw call runs. Stores still 0 (`NOWRITE-CONFIRMED +> wrote=0`; two operand pages changed). +> - TCS-off (`45dbcdcd`, eng65) clears the DS latch entirely (the +> `0x84000420` was the synthesized TCS bind); c792 has no `DS-FAST` line. +> - The `DRAW_IAB` body was decoded with the public Mesa MME toolchain +> (`mme_tu104_sim`): slot 34 (`0x265`) is a 25-instruction macro that emits +> **8 draws of 3 vertices** (`SET_VERTEX_ARRAY_START` 0..21, +> `DRAW_VERTEX_ARRAY` 3). The macro is correct; the no-store cause is +> downstream. +> - eng66-68 (`ef2e68b9`, `dab4a02c`, `3481e62d`): DRAW-STATE/CALL-ARGS +> census, synthetic full-RT viewport, release chained after any GR launch. +> - eng69-74 (`5ff47a95`..`88d5005a`): vertex-stream census/persistence and +> `sema_gl_vs_autobind` (scan a launch data page for a float2 vertex block +> and prepend VS0 + the Turing size pair on release saves); `GUEST-WIT` +> widened to launch pages and the big-surface alias pages. +> - c807/c811/c817/c819/c820/c822/c823: the replay is now **syntactically +> complete** — call order, SA[34], DS (TCS-off clean), viewport 1920x1080, +> RT0/RT1 alias, nonzero `VS0`/`SZ0`, `mac=0x22` — yet the render target +> still receives nothing (`wrote=0`, `0/1025`) and `GUEST-WIT` shows only +> CB/GR-context/report pages written. The 151-word DRAW window carries no +> vertex format/location/size at all, and the client's captured pushes +> never bind the stream directly (the only `0x1c00` census hits are +> SPH-payload false positives). +> - **Remaining hard blockers:** (a) the true per-draw vertex buffer is +> unidentified (the eng71 scan's CB-page candidate is a heuristic, score 8; +> a nonzero stale `VS0` also stores nothing); (b) render-target +> store/alias visibility is unproven (the big-surface alias pages do not +> populate the WIT, so an RT store would be invisible today). eng74 (`88d5005a`) +> dumps the scanned candidate blob (`VS-BLOB`) and records the +> surface-alias RT pages in the `GUEST-WIT`, so both blockers are +> measurable on the next boot. +> - Throughput: the pack-completion and shallow-boot/X-start lotteries +> continue (c783-c785, c789-c791, c804 shallow; c823 ran 4 frames black). +> +> CUDA front unchanged (backgrounded while graphics holds the device; its +> 10-30 status stands): `41343c63` green (`victory_mail` `VADD bad=0` + +> `STATUS OK`; `vecadd_loop` 100 launches PASS); the fresh-boot battery's red +> class is D2H-stage with release-discipline fixes staged; the SESSION 143 +> Vulkan fence regression is not re-measured. +> +> Live at check (read-only): host uptime 14 h 32 m (boot 2026-11-15 ~10:03); +> `vgsp` loaded (refcount 0) + mdev +> `3b5523a9-ef3a-4f83-8091-da29dce26265` + QEMU cycle c823 (PID 109722, 12 GiB +> file-backed guest, kvmfr ivshmem, since 19:36); X alive (display-channel +> polls advancing); `nvidia-smi` reports no GPU (the claim is held); pstore +> empty; no Xid/Oops; no reboot during the check. The open-iov.org wiki was +> refreshed alongside this snapshot (11 pages, revs 24199-24209; 68 pages +> audited, 0 problems). +> > **Snapshot: 2026-11-15 ~16:35 (SESSION 157 continued; HEAD `6aeb20c7` == > `vgpu/master`; the working tree carries only this docs refresh; supersedes > the 2026-11-15 ~13:55 entry below).** diff --git a/wiki/.publish-manifest.json b/wiki/.publish-manifest.json index d135731..94d4cc9 100644 --- a/wiki/.publish-manifest.json +++ b/wiki/.publish-manifest.json @@ -64,11 +64,11 @@ }, "FAQ": { "file": "FAQ.wiki", - "new_revid": 24179, - "old_revid": 24168, - "source_sha": "a60d299efe4e8e8a", - "summary": "2026-11-15 evening refresh (HEAD 6aeb20c7): release path host-deterministic (c772), slot-34/SA[34] settled (0x265), reorder landed; blocker is call order; eng64 chains the release behind the pack carrier; DS 0x84000420/stores remain", - "timestamp": "2026-11-15T21:37:18Z", + "new_revid": 24201, + "old_revid": 24190, + "source_sha": "0eb614e09363c599", + "summary": "2026-11-16 status refresh (HEAD 88d5005a): DRAW_IAB mac=0x22 executes end to end (c788); TCS-off DS clean; remaining blockers = vertex buffer (eng74 VS-BLOB dumps the candidate) and render-target store/alias visibility (eng74 records the alias RT pages in WIT); stores 0", + "timestamp": "2026-11-16T05:38:39Z", "title": "FAQ" }, "GMMU Multi-Tenant Protection": { @@ -127,11 +127,11 @@ }, "Graphics Execution": { "file": "Graphics-Execution.wiki", - "new_revid": 24180, - "old_revid": 24169, - "source_sha": "69252ee5880d2ea0", - "summary": "2026-11-15 evening refresh (HEAD 6aeb20c7): release path host-deterministic (c772), slot-34/SA[34] settled (0x265), reorder landed; blocker is call order; eng64 chains the release behind the pack carrier; DS 0x84000420/stores remain", - "timestamp": "2026-11-15T21:37:19Z", + "new_revid": 24202, + "old_revid": 24191, + "source_sha": "34cd26041ed56af4", + "summary": "2026-11-16 status refresh (HEAD 88d5005a): DRAW_IAB mac=0x22 executes end to end (c788); TCS-off DS clean; remaining blockers = vertex buffer (eng74 VS-BLOB dumps the candidate) and render-target store/alias visibility (eng74 records the alias RT pages in WIT); stores 0", + "timestamp": "2026-11-16T05:38:39Z", "title": "Graphics Execution" }, "Guest Driver Lifecycle: A Field Guide": { @@ -226,11 +226,11 @@ }, "OpenGL": { "file": "OpenGL.wiki", - "new_revid": 24182, - "old_revid": 24171, - "source_sha": "18669a2422764d3b", - "summary": "2026-11-15 evening refresh (HEAD 6aeb20c7): release path host-deterministic (c772), slot-34/SA[34] settled (0x265), reorder landed; blocker is call order; eng64 chains the release behind the pack carrier; DS 0x84000420/stores remain", - "timestamp": "2026-11-15T21:37:20Z", + "new_revid": 24204, + "old_revid": 24193, + "source_sha": "f602534eaa8b1197", + "summary": "2026-11-16 status refresh (HEAD 88d5005a): DRAW_IAB mac=0x22 executes end to end (c788); TCS-off DS clean; remaining blockers = vertex buffer (eng74 VS-BLOB dumps the candidate) and render-target store/alias visibility (eng74 records the alias RT pages in WIT); stores 0", + "timestamp": "2026-11-16T05:38:40Z", "title": "OpenGL" }, "Performance": { @@ -244,38 +244,38 @@ }, "Physical GPU Backend and Guest Wiring": { "file": "Physical-GPU-Backend.wiki", - "new_revid": 24183, - "old_revid": 24172, - "source_sha": "28b0f988043208dc", - "summary": "2026-11-15 evening refresh (HEAD 6aeb20c7): release path host-deterministic (c772), slot-34/SA[34] settled (0x265), reorder landed; blocker is call order; eng64 chains the release behind the pack carrier; DS 0x84000420/stores remain", - "timestamp": "2026-11-15T21:37:20Z", + "new_revid": 24205, + "old_revid": 24194, + "source_sha": "a76ad03eb0698087", + "summary": "2026-11-16 status refresh (HEAD 88d5005a): DRAW_IAB mac=0x22 executes end to end (c788); TCS-off DS clean; remaining blockers = vertex buffer (eng74 VS-BLOB dumps the candidate) and render-target store/alias visibility (eng74 records the alias RT pages in WIT); stores 0", + "timestamp": "2026-11-16T05:38:41Z", "title": "Physical GPU Backend and Guest Wiring" }, "Project Goals": { "file": "Project-Goals.wiki", - "new_revid": 24184, - "old_revid": 24173, - "source_sha": "1bc4bffa2ee75b07", - "summary": "2026-11-15 evening refresh (HEAD 6aeb20c7): release path host-deterministic (c772), slot-34/SA[34] settled (0x265), reorder landed; blocker is call order; eng64 chains the release behind the pack carrier; DS 0x84000420/stores remain", - "timestamp": "2026-11-15T21:37:21Z", + "new_revid": 24206, + "old_revid": 24195, + "source_sha": "982fde8eab98b62f", + "summary": "2026-11-16 status refresh (HEAD 88d5005a): DRAW_IAB mac=0x22 executes end to end (c788); TCS-off DS clean; remaining blockers = vertex buffer (eng74 VS-BLOB dumps the candidate) and render-target store/alias visibility (eng74 records the alias RT pages in WIT); stores 0", + "timestamp": "2026-11-16T05:38:41Z", "title": "Project Goals" }, "Project Plan": { "file": "Project-Plan.wiki", - "new_revid": 24185, - "old_revid": 24174, - "source_sha": "8e662457fd35a307", - "summary": "2026-11-15 evening refresh (HEAD 6aeb20c7): release path host-deterministic (c772), slot-34/SA[34] settled (0x265), reorder landed; blocker is call order; eng64 chains the release behind the pack carrier; DS 0x84000420/stores remain", - "timestamp": "2026-11-15T21:37:21Z", + "new_revid": 24207, + "old_revid": 24196, + "source_sha": "8b97b136e3a0174e", + "summary": "2026-11-16 status refresh (HEAD 88d5005a): DRAW_IAB mac=0x22 executes end to end (c788); TCS-off DS clean; remaining blockers = vertex buffer (eng74 VS-BLOB dumps the candidate) and render-target store/alias visibility (eng74 records the alias RT pages in WIT); stores 0", + "timestamp": "2026-11-16T05:38:42Z", "title": "Project Plan" }, "Project Status": { "file": "Project-Status.wiki", - "new_revid": 24186, - "old_revid": 24175, - "source_sha": "ed8adbf6185d4dc6", - "summary": "2026-11-15 evening refresh (HEAD 6aeb20c7): release path host-deterministic (c772), slot-34/SA[34] settled (0x265), reorder landed; blocker is call order; eng64 chains the release behind the pack carrier; DS 0x84000420/stores remain", - "timestamp": "2026-11-15T21:37:21Z", + "new_revid": 24208, + "old_revid": 24197, + "source_sha": "0db90f5a36b02148", + "summary": "2026-11-16 status refresh (HEAD 88d5005a): DRAW_IAB mac=0x22 executes end to end (c788); TCS-off DS clean; remaining blockers = vertex buffer (eng74 VS-BLOB dumps the candidate) and render-target store/alias visibility (eng74 records the alias RT pages in WIT); stores 0", + "timestamp": "2026-11-16T05:38:42Z", "title": "Project Status" }, "RPC Message Format": { @@ -289,11 +289,11 @@ }, "System Overview": { "file": "System-Overview.wiki", - "new_revid": 24187, - "old_revid": 24176, - "source_sha": "8a03ffc5fd543d7f", - "summary": "2026-11-15 evening refresh (HEAD 6aeb20c7): release path host-deterministic (c772), slot-34/SA[34] settled (0x265), reorder landed; blocker is call order; eng64 chains the release behind the pack carrier; DS 0x84000420/stores remain", - "timestamp": "2026-11-15T21:37:22Z", + "new_revid": 24209, + "old_revid": 24198, + "source_sha": "a2cf31484e358cc4", + "summary": "2026-11-16 status refresh (HEAD 88d5005a): DRAW_IAB mac=0x22 executes end to end (c788); TCS-off DS clean; remaining blockers = vertex buffer (eng74 VS-BLOB dumps the candidate) and render-target store/alias visibility (eng74 records the alias RT pages in WIT); stores 0", + "timestamp": "2026-11-16T05:38:42Z", "title": "System Overview" }, "Template:About message": { @@ -325,11 +325,11 @@ }, "The Execution Frontier": { "file": "Execution-Frontier.wiki", - "new_revid": 24177, - "old_revid": 24166, - "source_sha": "694c4ae09c4cccec", - "summary": "2026-11-15 evening refresh (HEAD 6aeb20c7): release path host-deterministic (c772), slot-34/SA[34] settled (0x265), reorder landed; blocker is call order; eng64 chains the release behind the pack carrier; DS 0x84000420/stores remain", - "timestamp": "2026-11-15T21:37:17Z", + "new_revid": 24199, + "old_revid": 24188, + "source_sha": "e50fe513268107dc", + "summary": "2026-11-16 status refresh (HEAD 88d5005a): DRAW_IAB mac=0x22 executes end to end (c788); TCS-off DS clean; remaining blockers = vertex buffer (eng74 VS-BLOB dumps the candidate) and render-target store/alias visibility (eng74 records the alias RT pages in WIT); stores 0", + "timestamp": "2026-11-16T05:38:38Z", "title": "The Execution Frontier" }, "The Guest Stack and CUDASW": { @@ -343,20 +343,20 @@ }, "The Host Module (vgsp.ko)": { "file": "Host-Module.wiki", - "new_revid": 24181, - "old_revid": 24170, - "source_sha": "fde89d5868b93ea0", - "summary": "2026-11-15 evening refresh (HEAD 6aeb20c7): release path host-deterministic (c772), slot-34/SA[34] settled (0x265), reorder landed; blocker is call order; eng64 chains the release behind the pack carrier; DS 0x84000420/stores remain", - "timestamp": "2026-11-15T21:37:19Z", + "new_revid": 24203, + "old_revid": 24192, + "source_sha": "8d8062605fefe722", + "summary": "2026-11-16 status refresh (HEAD 88d5005a): DRAW_IAB mac=0x22 executes end to end (c788); TCS-off DS clean; remaining blockers = vertex buffer (eng74 VS-BLOB dumps the candidate) and render-target store/alias visibility (eng74 records the alias RT pages in WIT); stores 0", + "timestamp": "2026-11-16T05:38:40Z", "title": "The Host Module (vgsp.ko)" }, "The vGSP Execution Plane (vEP)": { "file": "Execution-Plane.wiki", - "new_revid": 24178, - "old_revid": 24167, - "source_sha": "4a78097d559d84dd", - "summary": "2026-11-15 evening refresh (HEAD 6aeb20c7): release path host-deterministic (c772), slot-34/SA[34] settled (0x265), reorder landed; blocker is call order; eng64 chains the release behind the pack carrier; DS 0x84000420/stores remain", - "timestamp": "2026-11-15T21:37:18Z", + "new_revid": 24200, + "old_revid": 24189, + "source_sha": "a181986add587fd9", + "summary": "2026-11-16 status refresh (HEAD 88d5005a): DRAW_IAB mac=0x22 executes end to end (c788); TCS-off DS clean; remaining blockers = vertex buffer (eng74 VS-BLOB dumps the candidate) and render-target store/alias visibility (eng74 records the alias RT pages in WIT); stores 0", + "timestamp": "2026-11-16T05:38:38Z", "title": "The vGSP Execution Plane (vEP)" }, "UVM in the Guest": { diff --git a/wiki/Execution-Frontier.md b/wiki/Execution-Frontier.md index 15396c6..4549f08 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 @ 6aeb20c7`. +Status: 2026-11-15, tree `master @ 88d5005a`. Tags: `[live]` observed; `[wip]` partial; `[wall]` current blocker; theories are labelled as such. @@ -131,17 +131,21 @@ 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 blocker is **call -order** — the saved 728-B state window places the slot-34 run after the -`0x33/0x39` setup, so the last `0x39` latches DS `0x84000420` and the MFE -never reaches CALL(34) (c780), while the 324-B DRAW window places it first -and ran `mac=0x22` (c716). A release-window reorder (`a03a68ea`) is landed -but unexercised, and pack completion is still a per-boot lottery (poisoned -pack-part; no pump pass after the carry arm; carry-armed-never-fired); -`6aeb20c7` (eng64) chains the release behind a successful pack carrier and -names a stalled carrier's gate, validation pending. The -DS still carries the stage type/context bits (SPH5/SPH10/SPH18), so the draw -does not store (`wrote=0`, `px0=0`); the window/screen +**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 @@ -221,14 +225,16 @@ populated. The **DS stage-0/1 image is now authored and live** (a VTG SPH at 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 remaining blocker is call order: the 728-B -state window places the slot-34 run after the `0x33/0x39` setup, so the `0x39` -DS latch pre-empts it (c780), while the 324-B DRAW window places it first and -ran `mac=0x22` (c716); the reorder `a03a68ea` is landed but unexercised, and -pack completion is still a per-boot lottery (`6aeb20c7`, eng64, chains the -release behind a successful pack carrier; validation pending). The DS stage -type/context bits (SPH5/SPH10/SPH18) remain after the call, so the draws -still do not store. +(`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 @@ -246,13 +252,14 @@ dominant throughput limiter 4. **Hold the acceptance battery** — vector-add, matrix-multiply and the transformer kernel; each entry is accepted only on its own verification output (`bad=0` + `STATUS OK`). -5. **The graphics pixel frontier** — the DS stage image is authored and live - for both vertex slots, and the saved-window release carrier now replays the - held window deterministically when the pack completes; next exercise the - release-window reorder so the slot-34 `DRAW_IAB` call runs before the setup - calls and stores (`wrote>0`) at the bound render target, then clear the DS - stage type/context bits, make the window/screen present land, and reduce - the per-boot binding/X start lottery so the proven off-screen frames become +5. **The graphics pixel frontier** — the released replay now executes the + draw macro (`DRAW_IAB`, `mac=0x22`, TCS-off DS clean, synthetic viewport, + chained release); next identify the draw's true vertex buffer (no captured + client push binds it; the eng71 scan candidate is a heuristic), make the + render-target store/alias visible (`GUEST-WIT` coverage of the big-surface + alias pages) so the draw stores (`wrote>0`) at the bound render target, + then make the window/screen present land, and reduce the per-boot + binding/X start lottery so the proven off-screen frames become window pixels; the lanes, the walls and the milestone ladder are on [`Graphics-Execution.md`](Graphics-Execution.md). diff --git a/wiki/Execution-Plane.md b/wiki/Execution-Plane.md index 4a84457..86a9d49 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-15, tree `master @ 6aeb20c7`. Tags: `[live]` proven with the +Status: 2026-11-15, tree `master @ 88d5005a`. 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. @@ -173,13 +173,18 @@ guest: push + QMD + GPFIFO entry + doorbell (BAR0 0x88704) the pack completes: the saved-window release carrier snapshots the held window and re-submits it with the calls released once the pack is resident (c772), and the held-CALL census plus the SA[34] golden fill prove the - slot-34 `DRAW_IAB` target (`client=golden=used=0x265`). No non-black + slot-34 `DRAW_IAB` target (`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 (`45dbcdcd`) clears + the DS latch (the `0x84000420` was the synthesized TCS bind), a synthetic + full-RT viewport (`dab4a02c`) and a chained release (`3481e62d`) complete + the replay, and the body decodes with the public Mesa MME toolchain + (`mme_tu104_sim`: 8 draws of 3 vertices). No non-black **window/screen** frame has been produced through the NVIDIA path yet: the - blocker is call order (the 728-B window places slot-34 after the `0x33/0x39` - setup, so the DS latch `0x84000420` pre-empts it; the 324-B window places it - first and ran `mac=0x22`), the reorder `a03a68ea` is landed but unexercised, - pack completion is still a per-boot lottery, the DS stage type/context bits - (SPH5/SPH10/SPH18) remain, and the draw does not store (`wrote=0`, + remaining blockers are the vertex buffer (no captured client push binds + the stream; the eng71 scan candidate is a heuristic) and render-target + store/alias visibility (the big-surface alias pages do not yet enter + `GUEST-WIT`), so the draw does not store (`wrote=0`, `0/1025`, `px0=0`); the window/screen present is unproven, and the per-boot binding plus X first-generation lottery is the throughput limiter. Those are the named blockers. The lanes and the ladder are on diff --git a/wiki/FAQ.md b/wiki/FAQ.md index b527ce2..7c7a0a0 100644 --- a/wiki/FAQ.md +++ b/wiki/FAQ.md @@ -5,7 +5,7 @@ > [`../docs/09-reference/glossary-and-faq.md`](../docs/09-reference/glossary-and-faq.md); > the docs tree wins on disagreement. -Status: 2026-11-15, tree `master @ 6aeb20c7`. +Status: 2026-11-15, tree `master @ 88d5005a`. ## Project and positioning @@ -62,13 +62,16 @@ populated. The DS stage-0/1 image is now authored and live: a VTG SPH at (reproduced on two boots). The release path is now host-deterministic when the pack completes (the saved-window release carrier replays the held window with the calls released; the held-CALL census plus the SA[34] golden fill -prove `client=golden=used=0x265`). Window and screen pixels are still the -wall: the blocker is call order (the 728-B window places the slot-34 -`DRAW_IAB` call after the `0x33/0x39` setup, so the `0x39` DS latch -`0x84000420` pre-empts it; the 324-B window places it first and ran -`mac=0x22`), the reorder `a03a68ea` is landed but unexercised, pack -completion is still a per-boot lottery, the DS stage type/context bits -(SPH5/SPH10/SPH18) remain, so the draw never stores, glxgears' window is +prove `client=golden=used=0x265`). **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 clears the DS latch (the `0x84000420` was +the synthesized TCS bind), a synthetic viewport and a chained release +complete the replay, and the body decodes with the public Mesa MME toolchain +(8 draws of 3 vertices). Window and screen pixels are still the wall: the +remaining blockers are the vertex buffer (no captured client push binds the +stream; the eng71 scan candidate is a heuristic) and render-target +store/alias visibility (the big-surface alias pages do not yet enter the +write-witness set), so the draw never stores, glxgears' window is black, and the per-boot binding plus X first-generation start lottery is the throughput limiter. The guest Vulkan pipeline runs end to end (device diff --git a/wiki/Graphics-Execution.md b/wiki/Graphics-Execution.md index 0b5d97c..34b8147 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 @ 6aeb20c7`. Tags: `[live]` observed end to +Status: 2026-11-15, tree `master @ 88d5005a`. Tags: `[live]` observed end to end; `[wip]` partially built; `[wall]` current blocker; `[target]` defined success state; `[planned]` designed, not built. @@ -138,22 +138,28 @@ fidelity: `MME-CARRY-COMPLETE`), 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`; `MME-GOLDEN sa-fill slot=34 entry=0x265`). The remaining - blocker is **call order**: the saved 728-B state window places the slot-34 - run at `off=0x340` after the `0x33/0x39` setup, so the last `0x39` latches - DS `0x84000420` and the MFE never reaches CALL(34) (c780 released - `0x33/0x39/0x0`); the 324-B DRAW window places it first (off `0x1c0`) and - ran `mac=0x22` (c716). A release-window reorder (`a03a68ea`: - `[head binds][slot-34 run][rest]`) is landed but not yet exercised, and - pack completion is still a per-boot lottery (poisoned pack-part; no pump - pass after the carry arm; carry-armed-never-fired); `6aeb20c7` (eng64) - chains the release behind a successful pack carrier and names a stalled - carrier's gate (`MME-CARRY-WAIT reason=...`), validation pending. The - remaining DS bits - are stage type/context (SPH5/SPH10/SPH18); stores still miss (`wrote=0`, - `px0=0`). The window/screen present is still the frontier (§6), and the - per-boot binding/X-first-generation lottery is the throughput limiter. - + used=0x265`; `MME-GOLDEN sa-fill slot=34 entry=0x265`). **The draw macro + now executes end to end.** c788 proved `DRAW_IAB` (`mac=0x22`) running on + the released held window after the `MME-DRAW-PLAN`/`MME-DRAW-MOVE` reorder + (`MME-FAST ... mac=0x22 run=1`), and the per-stage SPH disable (TCS off, + `45dbcdcd`) clears the DS latch entirely — the `0x84000420` was the + synthesized TCS bind. The DRAW_IAB body decodes with the public Mesa MME + 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. ## 4. The channel and object picture * **Every submission lives on a channel**: a GPFIFO ring plus engine objects, @@ -212,9 +218,10 @@ swaps, and the GR backend no longer times out (the pair-close/pair-safe (Xorg in the DDX vidheap scrub wait) is fixed (`df6e71bb`), the X 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 next step is - the release call order (slot-34 `DRAW_IAB` before the setup calls) so the - draw issues and stores, then the window/screen present path. + 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. 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 @@ -248,18 +255,21 @@ requires it switched off, along with any external poke. `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 remaining - blocker is **call order**: the 728-B state window places the slot-34 run - at `off=0x340` after the `0x33/0x39` setup, so the last `0x39` latches DS - `0x84000420` and the MFE never reaches CALL(34) (c780 released - `0x33/0x39/0x0`); the 324-B DRAW window places it first (off `0x1c0`) and - ran `mac=0x22` (c716). The reorder `a03a68ea` (`[head binds][slot-34 - run][rest]`) is landed but unexercised (the c781/c782 boots never completed - the pack), and pack completion is still a per-boot lottery (`6aeb20c7`, - eng64, chains the release behind a successful pack carrier and names the - stalled gate; validation pending). The remaining - DS bits are stage type/context (SPH5/SPH10/SPH18); stores still miss - (`wrote=0`, `px0=0`). Closed on the way: the QMD-carrier theory + 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 @@ -330,13 +340,13 @@ requires it switched off, along with any external poke. | Multi-part MME keep-window: multi-frame windows admitted; the 2799-word pack completes (2799/2799) | `[live]` | | Part-launch poison eliminated: client `SET_REPORT_SEMAPHORE`/`SET_NOTIFY` targets redirected to a mapped scratch slot (49 cycles, 0 poison, 0 MMU faults) | `[live]` | | First `MME-PACK-REARM` captured (engine-global completion plus keep-done-across-recycle); fixed-CB region aliased; released calls run macros | `[live]` | -| `DRAW_IAB` (`mac=0x22`) executes on the 324-B window class after a cross-lane `MME-PACK-REARM`; SPH-BIND prelude emits 84 words; DS stage VAs populate | `[live]` | -| 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` (`0x86040626 -> 0x84000420`, two boots) | `[live]` | -| Saved-window release carrier: the held window is snapshotted at `MME-CALL-HOLD` and re-submitted with calls released once the pack is resident (c772: save 240/68 -> fire -> synthetic `GR LAUNCH 0x6d6d6500` -> REARM -> DS `0x84000420`) | `[live]` | -| Held-CALL census + SA[34] golden fill: the slot-34 `DRAW_IAB` call is present in the saved 728-B window; `client=golden=used=0x265` (`MME-GOLDEN sa-fill slot=34 entry=0x265`) | `[live]` | -| Call order: the 728-B window places slot-34 at `off=0x340` after the `0x33/0x39` setup, so the `0x39` DS latch pre-empts CALL(34) (c780: `mac=0x33/0x39/0x0`); the reorder `a03a68ea` is landed but unexercised | `[wall]` | -| Pack-completion lottery (poisoned pack-part; no pump pass after the carry arm; carry-armed-never-fired) gates the deterministic release | `[wall]` | -| DS `0x84000420` (SPH5/SPH10/SPH18 stage type/context) after the draw-issue call; stores `wrote=0` | `[wall]` | +| `DRAW_IAB` (`mac=0x22`) executes on the released held window after the `MME-DRAW-PLAN`/`MME-DRAW-MOVE` reorder (c788: `MME-FAST ... mac=0x22 run=1`); the body decodes with the public Mesa MME toolchain (`mme_tu104_sim`: slot 34, 8 draws of 3 vertices) | `[live]` | +| 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]` | +| 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]` | | Non-black screen pixels from the emulated vGPU's 3D pipeline | `[wall]` | @@ -353,10 +363,10 @@ requires it switched off, along with any external poke. 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 draw macro executes, and the authored DS stage - image is fetched by both vertex slots, but the 728-B window places the - slot-34 draw-issue call after the setup calls (so the DS latch pre-empts it) - and the stores are still missing, so the window stays black. + 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. * 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 diff --git a/wiki/Host-Module.md b/wiki/Host-Module.md index de68e5c..88a0750 100644 --- a/wiki/Host-Module.md +++ b/wiki/Host-Module.md @@ -6,7 +6,7 @@ > source: [`../docs/03-architecture/06-host-module-and-hybrid-model.md`](../docs/03-architecture/06-host-module-and-hybrid-model.md); > the docs tree wins on disagreement with this page. > -> Status: 2026-11-15, tree `master @ 6aeb20c7`. Tags: `[live]` observed with +> Status: 2026-11-15, tree `master @ 88d5005a`. Tags: `[live]` observed with > the stock guest driver; `[wip]` demonstrated live, being productized; > `[gated]` implemented default-off behind supervised gates; `[wall]` known > blocking limit; `[target]` designed, not built; `[planned]` roadmap. @@ -149,11 +149,16 @@ path is now host-deterministic when the pack completes: the saved-window release carrier snapshots the held window and re-submits it with the calls released once the pack is resident (c772), and the held-CALL census plus the SA[34] golden fill prove the slot-34 `DRAW_IAB` target -(`client=golden=used=0x265`). The remaining GL gap is call order (the 728-B -window places slot-34 after the `0x33/0x39` setup, so the DS latch pre-empts -it; the 324-B window places it first and ran `mac=0x22`), the reorder -`a03a68ea` (landed, unexercised), the pack-completion lottery, the DS stage -type/context bits (SPH5/SPH10/SPH18), the stores, and the window/screen +(`client=golden=used=0x265`). **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 viewport +(`dab4a02c`) and a 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 GL gap is 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`), so the stores are still missing, and the window/screen present path, which currently stays black or wedges X. ## 6. Debug parameters diff --git a/wiki/OpenGL.md b/wiki/OpenGL.md index 8a5e256..4453c96 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 @ 6aeb20c7`. Tags: `[live]` observed with the +Status: 2026-11-15, tree `master @ 88d5005a`. Tags: `[live]` observed with the stock guest driver; `[wip]` partial; `[wall]` current blocker; `[target]` defined success state. @@ -102,13 +102,13 @@ Rated honestly, against the milestone ladder in the plan: | Multi-part MME keep-window: multi-frame windows admitted; the 2799-word pack completes (2799/2799) | `[live]` | | Part-launch poison eliminated: client `SET_REPORT_SEMAPHORE`/`SET_NOTIFY` targets redirected to a mapped scratch slot (49 cycles, 0 poison, 0 MMU faults) | `[live]` | | First `MME-PACK-REARM` captured (engine-global completion plus keep-done-across-recycle); fixed-CB region aliased; released calls run macros | `[live]` | -| `DRAW_IAB` (`mac=0x22`) executes on the 324-B window class after a cross-lane `MME-PACK-REARM`; SPH-BIND prelude emits 84 words; DS stage VAs populate | `[live]` | -| 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` (`0x86040626 -> 0x84000420`, two boots) | `[live]` | -| Saved-window release carrier: the held window is snapshotted at `MME-CALL-HOLD` and re-submitted with calls released once the pack is resident (c772: save 240/68 -> fire -> synthetic `GR LAUNCH 0x6d6d6500` -> REARM -> DS `0x84000420`) | `[live]` | -| Held-CALL census + SA[34] golden fill: the slot-34 `DRAW_IAB` call is present in the saved 728-B window; `client=golden=used=0x265` (`MME-GOLDEN sa-fill slot=34 entry=0x265`) | `[live]` | -| Call order: the 728-B window places slot-34 at `off=0x340` after the `0x33/0x39` setup, so the `0x39` DS latch pre-empts CALL(34) (c780: `mac=0x33/0x39/0x0`); the reorder `a03a68ea` is landed but unexercised | `[wall]` | -| Pack-completion lottery (poisoned pack-part; no pump pass after the carry arm; carry-armed-never-fired) gates the deterministic release | `[wall]` | -| DS `0x84000420` (SPH5/SPH10/SPH18 stage type/context) after the draw-issue call; stores `wrote=0` | `[wall]` | +| `DRAW_IAB` (`mac=0x22`) executes on the released held window after the `MME-DRAW-PLAN`/`MME-DRAW-MOVE` reorder (c788: `MME-FAST ... mac=0x22 run=1`); the body decodes with the public Mesa MME toolchain (`mme_tu104_sim`: slot 34, 8 draws of 3 vertices) | `[live]` | +| 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]` | +| 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]` | | 60 fps sustained, no forcing (M-GL4) | `[target]` | @@ -153,18 +153,23 @@ snapshots the held window and re-submits it with the calls released once the pack is resident (c772 end to end), and the held-CALL census plus the SA[34] golden fill prove the slot-34 `DRAW_IAB` call and its target are present (`MME-CALL-TARGET slot=34 method=0x3910 client=0x265 golden=0x265 -used=0x265`). The remaining blocker is **call order**: the saved 728-B state -window places the slot-34 run after the `0x33/0x39` setup, so the last `0x39` -latches DS `0x84000420` and the MFE never reaches CALL(34) (c780); the 324-B -DRAW window places it first and ran `mac=0x22` (c716). A release-window -reorder (`a03a68ea`) is landed but not yet exercised, and pack completion is -still a per-boot lottery (`6aeb20c7`, eng64, chains the release behind a -successful pack carrier and names the stalled gate; validation pending). -After that come the remaining DS stage type/context -bits (SPH5/SPH10/SPH18), the stores, 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. +used=0x265`). **The draw macro now executes end to end**: c788 ran +`DRAW_IAB` (`mac=0x22`) on a released held window after the +`MME-DRAW-PLAN`/`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). +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. ## 6. What is not claimed @@ -173,13 +178,12 @@ frame. 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 draw macro executes, and the authored DS stage image is - fetched by both vertex slots; the release carrier can now replay the held - window deterministically when the pack completes, but the 728-B window - places the slot-34 draw-issue call after the setup calls (so the DS latch - pre-empts it) and 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. + 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. * 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. diff --git a/wiki/Physical-GPU-Backend.md b/wiki/Physical-GPU-Backend.md index ef2dcd3..9d22979 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 @ 6aeb20c7`. Tags: `[live]` proven with the +Status: 2026-11-15, tree `master @ 88d5005a`. 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 `DRAW_IAB` macro executes, 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 release call order (`a03a68ea`), the pack-completion lottery, the stores 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), 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)) | ## 7. The execution frontier @@ -130,13 +130,19 @@ the DDX 3D replay executes, captured GL sections execute on the engine, and the first non-black GPU-rendered frames are proven (500/500 off-screen frames per run plus captured videos); the direct-GL submission is fully decoded (macro-driven) and its draw-state push reaches the engine, the MME pack -completes, the `DRAW_IAB` macro executes, the DS stage image is authored and +completes, the released replay executes `DRAW_IAB` (`mac=0x22`; c788 ran it +on a held window after the `MME-DRAW-MOVE` reorder, TCS-off clears the DS +latch, the synthetic viewport and chained release complete the replay, and +the body decodes with the public Mesa MME toolchain as 8 draws of 3 +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 release call order (`a03a68ea`, landed but -unexercised), the pack-completion lottery, the DS stage type/context bits, +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 compute work is the staged-transfer class (under repair), the every-boot diff --git a/wiki/Project-Goals.md b/wiki/Project-Goals.md index c45d9cc..e8c9c1c 100644 --- a/wiki/Project-Goals.md +++ b/wiki/Project-Goals.md @@ -10,7 +10,7 @@ > [`Execution-Frontier.md`](Execution-Frontier.md) and > [`Graphics-Execution.md`](Graphics-Execution.md). -Status: 2026-11-15, tree `master @ 6aeb20c7`. Tags: `[live]` working with the +Status: 2026-11-15, tree `master @ 88d5005a`. Tags: `[live]` working with the stock guest driver; `[wip]` in progress; `[planned]` designed, not built; `[target]` bring-up ahead; `[non-goal]` explicitly out of scope. @@ -51,7 +51,7 @@ drivers, no license.** | Stock guest driver initialisation | The unmodified driver probes, initialises and enumerates as on bare metal (`nvidia-smi`) | `[live]` — TU104 reference platform | | Full CUDA driver-API surface | Context creation, allocation, copies, free, destroy complete with correct results | `[live]` — the driver-API smoke prints `ALL OK`; the 64-byte payload round-trips | | CUDA kernel execution on real hardware | Verified guest kernels execute on the physical GPU, with engine-authored completions waking the guest | `[live]` — vector-add, matrix-multiply and transformer clients green on fresh boots; the staged-transfer class, the every-boot acceptance campaign and per-guest isolation are in progress ([`Execution-Frontier.md`](Execution-Frontier.md)) | -| OpenGL (3D graphics) | Stock guest GL applications render real pixels through the emulated vGPU | `[wip]` — the display/KMS stack and X run, the stock NVIDIA GLX path is fully green (`glxinfo -B` rc 0, OpenGL 4.6.0 direct, `glxgears` ~520 FPS), the 2D path is green, the DDX 3D replay executes, the X DDX/ScreenInit stability walls are closed (X green >10 minutes), captured GL sections execute on the engine, 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 `DRAW_IAB` macro executes, 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 (slot-34 census plus SA[34] golden fill prove `client=golden=used=0x265`), and the first non-black GPU-rendered frames plus captured videos (45.4 s and 50 s) are proven off-screen; GZDoom reaches `V_Init`. Window/screen pixels remain the frontier: the release call order (`a03a68ea`, landed but unexercised), the pack-completion lottery, the remaining DS stage type/context bits and the stores are the last named gates before window pixels, the window/screen present is unproven, and the per-boot binding/X first-generation lottery is the throughput limiter ([`OpenGL.md`](OpenGL.md)) | +| OpenGL (3D graphics) | Stock guest GL applications render real pixels through the emulated vGPU | `[wip]` — the display/KMS stack and X run, the stock NVIDIA GLX path is fully green (`glxinfo -B` rc 0, OpenGL 4.6.0 direct, `glxgears` ~520 FPS), the 2D path is green, the DDX 3D replay executes, the X DDX/ScreenInit stability walls are closed (X green >10 minutes), captured GL sections execute on the engine, 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 (slot-34 census plus SA[34] golden fill prove `client=golden=used=0x265`), and the first non-black GPU-rendered frames plus captured videos (45.4 s and 50 s) are proven off-screen; GZDoom reaches `V_Init`. Window/screen pixels remain the frontier: the vertex-buffer identity and the render-target store/alias visibility are the last named gates before window pixels, the window/screen present is unproven, the pack-completion lottery limits the release, and the per-boot binding/X first-generation lottery is the throughput limiter ([`OpenGL.md`](OpenGL.md)) | | Vulkan | Stock guest Vulkan applications render real pixels | `[wip]` — the pipeline runs end to end (device → command buffer → fence → readback); frames are black — program delivery and program-VA mapping are the frontier ([`Vulkan.md`](Vulkan.md)) | | Windows guests (DirectX, CUDA) | A stock WDDM driver and stock D3D/CUDA applications run in Windows guests | `[target]` — not started; same emulation target ([`DirectX.md`](DirectX.md)) | | Video (NVENC/NVDEC) | Encode/decode through the emulated device | `[planned]` | diff --git a/wiki/Project-Plan.md b/wiki/Project-Plan.md index 2594282..102359f 100644 --- a/wiki/Project-Plan.md +++ b/wiki/Project-Plan.md @@ -15,7 +15,7 @@ > [`../docs/06-portability/03-device-validation-and-porting-sequence.md`](../docs/06-portability/03-device-validation-and-porting-sequence.md); > the docs tree wins on disagreement. -Status: 2026-11-15, tree `master @ 6aeb20c7`. Tags: `[done]`, `[active]`, +Status: 2026-11-15, tree `master @ 88d5005a`. Tags: `[done]`, `[active]`, `[ahead]` — the plan's own state vocabulary, distinct from the goal tags. ## 1. How the plan works @@ -44,7 +44,7 @@ itself: |---|---|---|---| | **P0 — Platform** | Emulated vGPU device, GSP boot and GSP-RM emulation, stock guest driver initialisation | Driver-API smoke green (`ALL OK`) = evaluation rung 2 | `[done]` | | **P1 — First execution (compute)** | Guest CUDA kernels executing on the physical GPU, with engine-authored completions; then hardening | Verified clients + engine-authored completion = rung 3 core; hardening: staged-transfer class, every-boot acceptance, per-guest isolation | `[active]` — execution green; hardening in progress | -| **P2 — Graphics execution** | OpenGL/Vulkan draw commands executed by the physical 3D pipeline and delivered as readable pixels | The graphics ladder: M-GL1 client context-init executes; M-GL2 `glxgears` non-black; M-GL3 GZDoom GL non-black through the mdev | `[active]` — between M-GL1 and M-GL2 with M-GL2's off-screen half proven: the display/KMS and DDX replay machinery work, X + stock GLX are green, the first non-black GPU-rendered frames and videos are captured, the X DDX/ScreenInit stability walls are closed, captured GL sections execute on the engine, 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 `DRAW_IAB` macro executes, the DS stage image is authored and live for both vertex slots (`st0=st1=020a0481`), and the saved-window release carrier deterministically replays the held window once the pack is resident; the remaining walls are the release call order (`a03a68ea`, landed but unexercised), the pack-completion lottery, the remaining DS stage type/context bits and the stores, the window/screen present, and the per-boot binding/X first-generation start lottery | +| **P2 — Graphics execution** | OpenGL/Vulkan draw commands executed by the physical 3D pipeline and delivered as readable pixels | The graphics ladder: M-GL1 client context-init executes; M-GL2 `glxgears` non-black; M-GL3 GZDoom GL non-black through the mdev | `[active]` — between M-GL1 and M-GL2 with M-GL2's off-screen half proven: the display/KMS and DDX replay machinery work, X + stock GLX are green, the first non-black GPU-rendered frames and videos are captured, the X DDX/ScreenInit stability walls are closed, captured GL sections execute on the engine, 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`), and the saved-window release carrier deterministically replays the held window once the pack is resident; the remaining walls are the vertex-buffer identity, the render-target store/alias visibility, the pack-completion lottery, the stores, the window/screen present, and the per-boot binding/X first-generation start lottery | | **P3 — Sustained and multi-tenant** | Frame rates without assistance; multiple VMs sharing the GPU with measured fairness; soak-stable operation | Graphics M-GL4 (60 fps, no forcing) and M-GL5 (two VMs, two mdevs); CUDA battery + soak; per-guest execution isolation = rungs 4/5 | `[ahead]` | | **P4 — Breadth** | Video (NVENC/NVDEC), Windows/DirectX guests, live migration, non-KVM hypervisor transports | Per-case bring-up gates plus the matrix's evidence expectations | `[ahead]` | | **P5 — Scale and portability** | New GPU generations and driver families carried forward; published performance programme | A profile + measured delta per version, validated on hardware; A/B numbers published per the measurement contract | `[ahead]` | @@ -72,14 +72,20 @@ Ranked, in dependency order: path is now host-deterministic when the pack completes: the saved-window release carrier replays the held window with the calls released, and the slot-34 census plus the SA[34] golden fill prove - `client=golden=used=0x265`. The named walls are the release call order - (the 728-B window places slot-34 after the `0x33/0x39` setup, so the DS - latch pre-empts it; the reorder `a03a68ea` is landed but unexercised), the - pack-completion lottery, the remaining DS stage type/context bits - (SPH5/SPH10/SPH18) and the stores, the window/screen present path - (glxgears' window is black and a window draw wedges X), the per-boot - binding/X first-generation start lottery (even `modeNum` required; now the - dominant throughput limiter), and then non-black window frames. + `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 (`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 named walls are + the vertex-buffer identity (no captured client push binds the stream; the + eng71 scan candidate is a heuristic, with eng74 `VS-BLOB` dumping it) and + the render-target store/alias visibility (the big-surface alias pages do + not yet enter `GUEST-WIT`; eng74 records them), the + pack-completion lottery, the stores, the window/screen present path + (glxgears' window is black and a window draw wedges X), the per-boot + binding/X first-generation start lottery (even `modeNum` required; now the + dominant throughput limiter), and then non-black window frames. Full detail: [`Graphics-Execution.md`](Graphics-Execution.md) §6. 2. **Compute hardening (P1).** The staged-transfer class (failure modes proven, diff --git a/wiki/Project-Status.md b/wiki/Project-Status.md index 6b1438a..78e6d12 100644 --- a/wiki/Project-Status.md +++ b/wiki/Project-Status.md @@ -10,7 +10,7 @@ > (the execution frontier). When this page and the docs disagree, the docs tree > wins. -Status: 2026-11-15, tree `master @ 6aeb20c7`. Tags: `[live]` proven with the +Status: 2026-11-15, tree `master @ 88d5005a`. Tags: `[live]` proven with the stock guest driver; `[gated]` implemented, default-off or behind supervised gates; `[wip]` partially implemented; `[wall]` current blocker; `[target]` named success state; `[planned]` designed, not built. @@ -28,7 +28,7 @@ named success state; `[planned]` designed, not built. | Physical backend on real hardware (module-owned GPU running its real GSP-RM) | `[live]` boot, RPC session, object creation, copy-engine work and GR execution proven — the verified guest CUDA kernel clients execute through this backend, and graphics method streams execute on the engine ([`Graphics-Execution.md`](Graphics-Execution.md)) | | Display and KMS on the emulated vGPU (nvidia-modeset/NvKms, `/dev/dri`, X) | `[live]` in the campaign configuration — the emulated display engine serves the guest's display push-buffer channels (notifier plus `UPDATE -> FINISHED`), nvidia-modeset/NvKms registers (`/dev/dri/card0`, `renderD128`, `fb0`), `nvidia-smi -L` enumerates and X settles. The X DDX idle-DMA/ScreenInit, USERD-latch lifetime, re-probe-thrash, Xorg kernel-mode-spin and flip-event walls were closed (X green for >10 minutes in a validated window); what remains is the per-boot **first-generation X start lottery**, which by 11-13/11-14 was the dominant throughput limiter for the graphics A/B runs (only an X started immediately after boot passes DDX DMA init; long stretches of dead starts, one green first-start boot). The display-capability seam is parameterised ([`Graphics-Execution.md`](Graphics-Execution.md)) | | Multi-tenant isolation (mdev per VM, per-context page directories) | `[wip]` device-level coexistence works — multiple mediated devices with different emulated VRAM sizes and multiple guests coexist (two guests demonstrated); per-guest execution isolation for simultaneous CUDA guests is in progress | -| OpenGL (3D graphics) | `[wip]` — the display/KMS stack registers, X and the stock NVIDIA GLX path are fully green (`glxinfo -B` returns 0 with OpenGL 4.6.0 and direct rendering; `glxgears` renders ~520 FPS with the emulated GPU's NVIDIA renderer), and the **first non-black GPU-rendered output** is proven: the pbuffer frame path produced 500/500 non-black 640x480 frames per run and captured videos (45.4 s on 2026-11-11; a 50 s 640x480 h264 capture on 2026-11-12). GZDoom reaches `V_Init: allocate screen` with its GL 4.6.0 context whenever the shared nvClip `modeNum` is even. **The direct-GL submission is now fully decoded:** no client push carries a method-grammar draw header — the channel's 9 NV906F entries tile one contiguous buffer and its per-frame work is carried as rewritten data-block blobs plus small state pushes (324/476/728 B) that invoke MME macros (the QMD-carrier hypothesis was tested and refuted). A content-gated FB-shadow rescue and a LOW-band rescue recover the recycled pushes: the client's draw-state push now opens a C597 section, is captured and marked for the verbatim 3D lane (the first direct-GL stream3d marks), and reaches the engine (`GR LAUNCH submitted`/`OK`, golden MME overlay accepted). **The MME chain now completes and executes the draw macro.** The multi-part keep-window mechanism won multi-frame windows; the part-launch poison was eliminated (the real fault was the client's own `SET_REPORT_SEMAPHORE`/`SET_NOTIFY` writes to client VAs that the host scratch page-table pool remaps — redirected to a mapped scratch slot; 49 cycles with zero poison and zero MMU faults); the 2799-word pack completes (2799/2799); engine-global completion plus keep-done-across-recycle produced the first `MME-PACK-REARM`; the fixed-CB region is aliased; and the released calls run macros through to **`DRAW_IAB` (`mac=0x22`)**. Two synthesized-prelude defects were then fixed: the SPH-BIND prelude self-destructed because an auto-dropped run broke its kept/final count (`444ae2c1`), and the stage block was silently skipped by a double-counted budget; with both fixed the prelude emits 84 words and the DS stage VAs populate (one validated boot carried the full post-REARM chain, `mac=0x22` and `DS 86040624`). **The DS stage-0/1 image is now authored and live**: a VTG SPH is written at `family+0x900` (`SPH-AUTHOR`, first word `020a0481`), the window's own later `0x2054` slot-1 bind is rewritten to the authored page (`SPH-SLOT1-REWRITE`), and the DS latch reads the authored image for both vertex slots (`DS-IMAGE st0=st1=020a0481 code=ff007321`; the DS value fell `0x86040626 -> 0x84000420`), reproduced on two boots. The release path is now host-deterministic when the pack completes (the saved-window release carrier replays the held window with the calls released; the slot-34 census and SA[34] golden fill prove `client=golden=used=0x265`). The blocker is **call order**: the 728-B window places the slot-34 `DRAW_IAB` run after the `0x33/0x39` setup, so the `0x39` DS latch (`0x84000420`) pre-empts it; the 324-B window places it first and ran `mac=0x22`. A release-window reorder (`a03a68ea`) is landed but unexercised, pack completion is still a per-boot lottery (`6aeb20c7`, eng64, chains the release behind a successful pack carrier and names the stalled gate; validation pending), and the remaining DS stage type/context bits (SPH5/SPH10/SPH18) leave the stores missing (`wrote=0`, `px0=0`); the window/screen present path is unproven; and the per-boot binding lottery (the GL client usually rides the X channel in indirect mode, and X start keeps a first-generation lottery) is the throughput limiter ([`OpenGL.md`](OpenGL.md)) | +| OpenGL (3D graphics) | `[wip]` — the display/KMS stack registers, X and the stock NVIDIA GLX path are fully green (`glxinfo -B` returns 0 with OpenGL 4.6.0 and direct rendering; `glxgears` renders ~520 FPS with the emulated GPU's NVIDIA renderer), and the **first non-black GPU-rendered output** is proven: the pbuffer frame path produced 500/500 non-black 640x480 frames per run and captured videos (45.4 s on 2026-11-11; a 50 s 640x480 h264 capture on 2026-11-12). GZDoom reaches `V_Init: allocate screen` with its GL 4.6.0 context whenever the shared nvClip `modeNum` is even. **The direct-GL submission is now fully decoded:** no client push carries a method-grammar draw header — the channel's 9 NV906F entries tile one contiguous buffer and its per-frame work is carried as rewritten data-block blobs plus small state pushes (324/476/728 B) that invoke MME macros (the QMD-carrier hypothesis was tested and refuted). A content-gated FB-shadow rescue and a LOW-band rescue recover the recycled pushes: the client's draw-state push now opens a C597 section, is captured and marked for the verbatim 3D lane (the first direct-GL stream3d marks), and reaches the engine (`GR LAUNCH submitted`/`OK`, golden MME overlay accepted). **The MME chain now completes and executes the draw macro.** The multi-part keep-window mechanism won multi-frame windows; the part-launch poison was eliminated (the real fault was the client's own `SET_REPORT_SEMAPHORE`/`SET_NOTIFY` writes to client VAs that the host scratch page-table pool remaps — redirected to a mapped scratch slot; 49 cycles with zero poison and zero MMU faults); the 2799-word pack completes (2799/2799); engine-global completion plus keep-done-across-recycle produced the first `MME-PACK-REARM`; the fixed-CB region is aliased; and the released calls run macros through to **`DRAW_IAB` (`mac=0x22`)**. Two synthesized-prelude defects were then fixed: the SPH-BIND prelude self-destructed because an auto-dropped run broke its kept/final count (`444ae2c1`), and the stage block was silently skipped by a double-counted budget; with both fixed the prelude emits 84 words and the DS stage VAs populate (one validated boot carried the full post-REARM chain, `mac=0x22` and `DS 86040624`). **The DS stage-0/1 image is now authored and live**: a VTG SPH is written at `family+0x900` (`SPH-AUTHOR`, first word `020a0481`), the window's own later `0x2054` slot-1 bind is rewritten to the authored page (`SPH-SLOT1-REWRITE`), and the DS latch reads the authored image for both vertex slots (`DS-IMAGE st0=st1=020a0481 code=ff007321`; the DS value fell `0x86040626 -> 0x84000420`), reproduced on two boots. The release path is now host-deterministic when the pack completes (the saved-window release carrier replays the held window with the calls released; the slot-34 census and SA[34] golden fill prove `client=golden=used=0x265`). The remaining blockers are the vertex buffer (no captured client push binds the stream; the eng71 scan candidate is a heuristic, with eng74 `VS-BLOB` dumping it for validation) and render-target store/alias visibility (the big-surface alias pages do not yet enter `GUEST-WIT`; eng74 now records them), so the stores are still missing (`wrote=0`, `0/1025`, `px0=0`); the window/screen present path is unproven; and the per-boot binding lottery (the GL client usually rides the X channel in indirect mode, and X start keeps a first-generation lottery) is the throughput limiter ([`OpenGL.md`](OpenGL.md)) | | Vulkan (3D/compute) | `[wip]` — the guest Vulkan pipeline runs end to end on the emulated vGPU (device, allocation, pipeline, command buffer, fence, queue submit, readback) and the engine executes translated launches; frames are still black — program delivery and program-VA mapping are the frontier ([`Vulkan.md`](Vulkan.md)) | | DirectX / Windows guests | `[planned]` (target) — no Windows guest booted yet; the architecture is the same emulation target ([`DirectX.md`](DirectX.md)) | | Video (NVENC/NVDEC) | `[planned]` | @@ -81,12 +81,12 @@ GPU-rendered frames are proven off-screen (the pbuffer path produced a 500-frame 45.4 s video on 2026-11-11 and a 50 s capture on 2026-11-12), and GZDoom reaches its screen-allocation stage with GL 4.6.0 on an even modeNum. The direct-GL submission is fully decoded, the MME multi-part program now -completes and the draw macro executes, and the DS stage image is authored and -live for both vertex slots; the saved-window release carrier now replays the -held window deterministically when the pack completes, but windowed/screen -pixels remain the frontier (the release call order, the pack-completion -lottery and the stores are the next named gates, and X start keeps a -first-generation lottery) — see [`OpenGL.md`](OpenGL.md). The +completes and the released replay executes the draw macro (`DRAW_IAB`, +`mac=0x22`, with a synthetic viewport; c788), and the DS stage image is +authored and live for both vertex slots; but windowed/screen pixels remain +the frontier (the vertex-buffer identity, the render-target store/alias +visibility and the pack-completion lottery are the next named gates, and X +start keeps a first-generation lottery) — see [`OpenGL.md`](OpenGL.md). The risc-v-gsp-rm-debugger workbench ([`Riscv-GSP-RM-Debugger.md`](Riscv-GSP-RM-Debugger.md)) is the host-side tooling used to study the firmware side of that frontier. diff --git a/wiki/System-Overview.md b/wiki/System-Overview.md index 87732ca..667dfb3 100644 --- a/wiki/System-Overview.md +++ b/wiki/System-Overview.md @@ -7,7 +7,7 @@ > and [`../docs/03-architecture/10-interaction-and-scheduling.md`](../docs/03-architecture/10-interaction-and-scheduling.md) > for the full picture); the docs tree wins on disagreement. -Status: 2026-11-15, tree `master @ 6aeb20c7`. Tags: `[live]` proven with the +Status: 2026-11-15, tree `master @ 88d5005a`. Tags: `[live]` proven with the stock guest driver; `[gated]` implemented default-off; `[wip]` partial; `[wall]` current blocker; `[target]` designed end state. @@ -162,17 +162,22 @@ RPC from the guest to "firmware": `0x86040626 -> 0x84000420`, two boots). The release path is now host-deterministic when the pack completes (the saved-window release carrier replays the held window with calls released; the slot-34 census - plus SA[34] golden fill prove `client=golden=used=0x265`). The remaining - gates are the release call order (the 728-B window places slot-34 after - the `0x33/0x39` setup, so the DS latch pre-empts it; the 324-B window ran - `mac=0x22`; the reorder `a03a68ea` is landed but unexercised), the - pack-completion lottery, the DS stage type/context bits (SPH5/SPH10/SPH18), - the stores (`wrote=0`, `px0=0`), and the window/screen present (a window - draw can wedge X and glxgears' window is black); the per-boot binding plus - X first-generation start lottery is the dominant throughput limiter, so the - remaining gates are the call-order/store and the window/screen present - before the first non-black window frame - ([`OpenGL.md`](OpenGL.md), [`Vulkan.md`](Vulkan.md)). + plus SA[34] golden fill prove `client=golden=used=0x265`). **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 clears the DS latch + (the `0x84000420` was the synthesized TCS bind), a synthetic viewport and a + chained release complete the replay, and the body decodes with the public + Mesa MME toolchain (8 draws of 3 vertices). The remaining + gates are the vertex-buffer identity (no captured client push binds the + stream; the eng71 scan candidate is a heuristic) and the render-target + store/alias visibility (the big-surface alias pages do not yet enter + `GUEST-WIT`), the pack-completion lottery, the stores (`wrote=0`, `0/1025`, + `px0=0`), and the window/screen present (a window + draw can wedge X and glxgears' window is black); the per-boot binding plus + X first-generation start lottery is the dominant throughput limiter, so the + remaining gates are the vertex/store and the window/screen present + before the first non-black window frame + ([`OpenGL.md`](OpenGL.md), [`Vulkan.md`](Vulkan.md)). ## 6. Where the detail lives -- cgit v1.2.3