diff options
| author | Arthur Hanson Rasmusson <arthur@vgpu.io> | 2026-11-17 01:19:29 -0500 |
|---|---|---|
| committer | Arthur Hanson Rasmusson <arthur@vgpu.io> | 2026-11-17 01:19:29 -0500 |
| commit | 3a0a1eba404919951ca3333ae9492f7213e60f75 (patch) | |
| tree | ada9df699ac9b0c7051e61dc3c73005e15c01225 /wiki/Project-Plan.md | |
| parent | 1db3831e8f1c40f8e65e86dc38d457aa494c9172 (diff) | |
| download | open-iov-3a0a1eba404919951ca3333ae9492f7213e60f75.tar.gz open-iov-3a0a1eba404919951ca3333ae9492f7213e60f75.zip | |
docs(wiki): 2026-11-17 status refresh - real GPU-GL draw admitted/replayed; per-draw MME macro body is the gateHEADmaster
- 11 wiki pages refreshed: the offscreen EGL/GBM shim gives the guest a real
NVIDIA GL context without Xorg/DDX; the real GZDoom draw window (12068 B
at push 0x402f9d8, op=4 CALL(0) 0x3800 imm 0xd48 plus slots 44/57/58) is
recognised, admitted bind-free, chunked and replayed verbatim.
- CALL(0) executes without trapping (eng89t resolve through client SA[0]
then golden, not-resident calls elided); c1026/c1027 entered the captured
macro and c1027 reached the first DS with real stage data. Trap 0x80001528
decoded as a sticky TRAPPED_ADDR latch, not a cause/PC.
- Remaining gate recorded precisely: the client's per-draw MME macro body was
never captured (the prelude carries only the 12 setup macros), with the
synthetic golden body the surviving wedge; stores still wrote=0, no px.
- STATE-CURRENT.md snapshot prepended; wiki published to open-iov.org
(revs 24221-24231; 68 pages audited, 0 problems).
Diffstat (limited to 'wiki/Project-Plan.md')
| -rw-r--r-- | wiki/Project-Plan.md | 34 |
1 files changed, 19 insertions, 15 deletions
diff --git a/wiki/Project-Plan.md b/wiki/Project-Plan.md index 889ca87..9970e09 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-16, tree `master @ a06d4b13`. Tags: `[done]`, `[active]`, +Status: 2026-11-17, tree `master @ 1db3831e`. Tags: `[done]`, `[active]`, `[ahead]` — the plan's own state vocabulary, distinct from the goal tags. ## 1. How the plan works @@ -40,11 +40,11 @@ itself: ## 2. The phases -| Phase | What it delivers | Exit gate | State (2026-11-16) | +| Phase | What it delivers | Exit gate | State (2026-11-17) | |---|---|---|---| | **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 released replay executes `DRAW_IAB` (`mac=0x22`, c788), and the 11-16 wave proved the host-side chain deterministic end to end (real frame pushes admitted with a persisted colour-target bind, a 40-chunk full-window replay and a 128-slot ring; a clean DS `DS-FAST2 ds_after=80000000` at the live-derived GS map; a golden 2799-word MME pack; CALL hold/carry fire/SA re-arm with the latch kept across the channel recycle). The decisive finding is guest-side: across 36 boots the client never submitted a non-null `CALL(34)` draw macro, and the same cycles logged guest EGL/dri2 failures and OOM kills; the remaining walls are a real guest draw submission, the vertex/store, the window/screen present, and the per-boot X first-generation start lottery. A GZDoom video was separately delivered through the guest's software GL path (Mesa llvmpipe) — not a vGPU rendering claim | +| **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 released replay executes `DRAW_IAB` (`mac=0x22`, c788), and the 11-16 wave proved the host-side chain deterministic end to end (real frame pushes admitted with a persisted colour-target bind, a 40-chunk full-window replay and a 128-slot ring; a clean DS `DS-FAST2 ds_after=80000000` at the live-derived GS map; a golden 2799-word MME pack; CALL hold/carry fire/SA re-arm with the latch kept across the channel recycle). The late-11-16 wave crossed the guest submission gap: an offscreen EGL/GBM shim gives GZDoom a real NVIDIA GL context without Xorg/DDX, and the real op=4 `CALL(0)` `0x3800` draw (12068 B at push `0x402f9d8`) is admitted and replayed; `CALL(0)` executes its captured macro without trapping (eng89t), and c1027 reached the first DS with real stage data. The remaining walls are the client's per-draw MME macro body (never captured; the prelude carries only the 12 setup macros, and the synthetic golden body is the surviving wedge), the vertex/store, the window/screen present, and the per-boot X first-generation start lottery. A GZDoom video was separately delivered through the guest's software GL path (Mesa llvmpipe) — not a vGPU rendering claim | | **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]` | @@ -83,18 +83,22 @@ counted runs, a 14.8-thousand-word window replayed as 40 chunks, a 128-slot candidate ring), a clean DS on the beef draw lane (`DS-FAST2 ds_after=80000000`, c963) at the live-derived GS map, a golden 2799-word MME pack on capture-less boots, and CALL hold/carry fire/SA re-arm 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 the same cycles logged guest EGL/dri2 failures and OOM kills. The named -walls are therefore a real guest draw submission first, then the -vertex/store, the window/screen present path (glxgears' window is black and -a window draw wedges X), and the per-boot X first-generation start lottery -(even `modeNum` required; the dominant 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. +prelude latch kept across the channel recycle. The **late-11-16 wave crossed the +guest submission gap**: an offscreen EGL/GBM shim gives GZDoom a real NVIDIA +GL context without Xorg/DDX (`GL_RENDERER: NVIDIA GeForce RTX 2080 +SUPER/PCIe/SSE2`, `GL_VERSION: 4.6.0 NVIDIA 570.144`; no llvmpipe), and the +real op=4 `CALL(0)` `0x3800` draw (12068 B at push `0x402f9d8`, slots +44/57/58) is admitted and replayed; `CALL(0)` executes its captured macro +without trapping (eng89t resolves the immediate through client SA[0]/golden +and elides not-resident calls), and c1027 reached the first DS with real +stage data. The named walls are therefore the client's per-draw MME macro +body (never captured; the prelude carries only the 12 setup macros, and the +synthetic golden body is the surviving wedge), then the vertex/store, the +window/screen present path (glxgears' window is black and a window draw +wedges X), and the per-boot X first-generation start lottery (even `modeNum` +required; the dominant 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. Full detail: [`Graphics-Execution.md`](Graphics-Execution.md) §6. 2. **Compute hardening (P1).** The staged-transfer class (failure modes proven, |
