diff options
Diffstat (limited to 'wiki/Execution-Frontier.md')
| -rw-r--r-- | wiki/Execution-Frontier.md | 24 |
1 files changed, 11 insertions, 13 deletions
diff --git a/wiki/Execution-Frontier.md b/wiki/Execution-Frontier.md index 18f150c..d90fdd7 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-09, tree `master @ cb8e822b`. +Status: 2026-11-09, tree `master @ bb802909`. Tags: `[live]` observed; `[wip]` partial; `[wall]` current blocker; theories are labelled as such. @@ -104,12 +104,11 @@ release applied); the direct GL client's GR and CE channels submit and retire, and the X DDX kick channel is decoded. GZDoom reached `MAP01` once the DDX push-buffer loop was unblocked, but on Mesa llvmpipe — not the emulated vGPU. What is missing is **rendered pixels through the NVIDIA path**: the GSP -event-IRQ fix completes swaps, the 2D path is green end-to-end, and the -guest's real GL draws now forward and execute on the physical GPU, but the -draw writes 0 pages because its constant-buffer (MVP) page is unresolved and -forced to the seed page; the MME front-end defer, the GR stale-wedge and the -DDX push-buffer get-word/notifier completion remain. The guest Vulkan -pipeline's inline-to-memory upload arm is its gap. The full +event-IRQ fix completes swaps, the 2D path is green end-to-end, X is reliable, +and the guest's real GL draws forward and execute on the physical GPU, but the +draw writes 0 pages. The beef GR ring resolution race, the fixed-CB image's +zero `0x80` MVP block and the render-target bind are the named walls. The +guest Vulkan pipeline's inline-to-memory upload arm is its gap. The full picture lives on [`Graphics-Execution.md`](Graphics-Execution.md). No breadth beyond these is claimed: Windows guests, migration and performance @@ -168,12 +167,11 @@ CUDA guests is in progress. **Issue D — the graphics pixel frontier.** The display/KMS stack and the GL client now run end to end (NvKms registers, X settles, GL 4.6, direct-GL -channels submit and retire, the X DDX waits are fixed), and the guest's real -GL draws forward and execute on the physical GPU; but the draw writes 0 pages -because its constant-buffer (MVP) page is unresolved and forced to the seed -page, and no rendered (non-black) frame has been produced yet. The constant -buffer, the MME front-end/stale-wedge stability and the DDX get-word/notifier -completion are the named blockers +channels submit and retire, the X DDX waits are fixed, X is reliable, and the +guest's real GL draws forward and execute on the physical GPU); but the draw +writes 0 pages and no rendered (non-black) frame has been produced yet. The +beef GR ring resolution, the fixed-CB image's zero MVP block and the +render-target bind are the named blockers ([`Graphics-Execution.md`](Graphics-Execution.md)). ## 6. Lines of investigation (live) |