summaryrefslogtreecommitdiffstats
path: root/wiki/Execution-Plane.md
diff options
context:
space:
mode:
authorArthur Hanson Rasmusson <arthur@vgpu.io>2026-11-16 22:55:55 -0500
committerArthur Hanson Rasmusson <arthur@vgpu.io>2026-11-16 22:55:55 -0500
commit6107a002a5fb532f0b673c107c4cbe5d0d8925b4 (patch)
tree36301e7d785c6855969d0145d6286552f443cc82 /wiki/Execution-Plane.md
parenta06d4b13cf209c2ce74a79a5565787e2edcbf0d8 (diff)
downloadopen-iov-6107a002a5fb532f0b673c107c4cbe5d0d8925b4.tar.gz
open-iov-6107a002a5fb532f0b673c107c4cbe5d0d8925b4.zip
docs(wiki): 2026-11-16 evening status refresh - host draw chain proven end to end, guest submission is the wall
- 11 wiki pages refreshed: the real frame pushes are admitted (persisted colour-target bind, draw markers inside counted runs, 40-chunk full-window replay, 128-slot ring); the beef draw lane latches a clean DS at the live-derived GS map; capture-less boots get the golden 2799-word MME pack; CALL hold/carry fire/SA re-arm fire with the latch kept across the channel recycle. - Decisive finding recorded as guest-side: 36 boots (c990-c1019) show no non-null CALL(34) draw macro from the client (interior 0x3910/0x3914 writes carry data=0x0) plus guest EGL/dri2 failures and OOM kills. - GZDoom video delivered via the guest software GL path (Mesa llvmpipe) is documented as a non-vGPU deliverable. - STATE-CURRENT.md snapshot prepended; wiki published to open-iov.org (revs 24210-24220; 68 pages audited, 0 problems).
Diffstat (limited to 'wiki/Execution-Plane.md')
-rw-r--r--wiki/Execution-Plane.md48
1 files changed, 21 insertions, 27 deletions
diff --git a/wiki/Execution-Plane.md b/wiki/Execution-Plane.md
index 86a9d49..d8786dd 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 @ 88d5005a`. Tags: `[live]` proven with the
+Status: 2026-11-16, tree `master @ a06d4b13`. Tags: `[live]` proven with the
stock guest driver; `[gated]` implemented, default-off or parameter-gated;
`[wip]` partial; `[wall]` current blocker; `[target]` named success latch;
`[planned]` designed, not built.
@@ -161,32 +161,26 @@ guest: push + QMD + GPFIFO entry + doorbell (BAR0 0x88704)
(no method-grammar draw header; the work is macro-driven — data-block blobs
plus small state pushes invoking MME macros), the recycled pushes are
recovered, and the client's draw-state push opens, captures and reaches the
- engine (`GR LAUNCH submitted` + OK, golden MME overlay accepted). The MME
- chain now completes and executes the draw macro: multi-frame keep-windows
- land, the 2799-word pack completes, the first `MME-PACK-REARM` fires, the
- fixed-CB region is aliased, and `DRAW_IAB` (`mac=0x22`) runs with the
- SPH-BIND prelude intact (84 words) and the DS stage VAs populated. The DS
- stage-0/1 image is now authored and live: a VTG SPH at `family+0x900`
- (first word `020a0481`) is fetched by both vertex slots
- (`DS-IMAGE st0=st1=020a0481`; DS fell `0x86040626 -> 0x84000420`,
- reproduced on two boots). The release 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 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
- 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
+ engine (`GR LAUNCH submitted` + OK, golden MME overlay accepted). The 11-16 wave then proved the
+ **host-side chain deterministic end to end**: the real frame pushes are
+ admitted (persisted colour-target bind, draw markers inside counted runs, a
+ 14.8-thousand-word window replayed as 40 chunks, a 128-slot candidate ring),
+ the beef draw lane latches a **clean DS** (`DS-FAST2 ... ds_after=80000000`,
+ c963) at the live-derived GS attribute map, capture-less boots get a
+ **golden 2799-word MME pack**, and `MME-CALL-HOLD -> MME-CARRY-SAVE ->
+ MME-CARRY-FIRE -> MME-PACK-REARM -> MME-SA-REARM` fires with the prelude
+ latch kept across the channel recycle. The **decisive finding is
+ guest-side**: across 36 boots (c990-c1019) the client never submitted 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 those cycles logged guest EGL/dri2 failures and OOM kills.
+ No non-black **window/screen** frame has been produced through the NVIDIA
+ path yet: the next work is guest-first (a real draw submission), then the
+ vertex/store and the window/screen present, with the per-boot X
+ first-generation lottery as the throughput limiter. 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.Those are the
named blockers. The lanes and the ladder are on
[`Graphics-Execution.md`](Graphics-Execution.md).