summaryrefslogtreecommitdiffstats
path: root/wiki/Graphics-Execution.md
diff options
context:
space:
mode:
Diffstat (limited to 'wiki/Graphics-Execution.md')
-rw-r--r--wiki/Graphics-Execution.md96
1 files changed, 53 insertions, 43 deletions
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