summaryrefslogtreecommitdiffstats
path: root/wiki/Physical-GPU-Backend.md
diff options
context:
space:
mode:
Diffstat (limited to 'wiki/Physical-GPU-Backend.md')
-rw-r--r--wiki/Physical-GPU-Backend.md10
1 files changed, 5 insertions, 5 deletions
diff --git a/wiki/Physical-GPU-Backend.md b/wiki/Physical-GPU-Backend.md
index 6b64d46..240e8fe 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-09, tree `master @ cb8e822b`. Tags: `[live]` proven with the
+Status: 2026-11-09, tree `master @ bb802909`. Tags: `[live]` proven with the
stock guest driver; `[gated]` implemented default-off; `[wip]` partially
built; `[wall]` current blocker; `[target]` planned end state.
@@ -123,10 +123,10 @@ same machinery in three shapes (a verbatim 3D method-stream replay,
synthesized launches, and the direct GL client's own GR/CE channels); the
captured and synthesized streams execute on the engine, and the direct GL
client's channels submit. The display/KMS stack registers, the X DDX waits are
-fixed, X settles and the guest's real GL draws forward and execute on the
-physical GPU, so the remaining graphics gates are the constant-buffer (MVP)
-content, the MME front-end/stale-wedge stability, and the DDX push-buffer
-get-word/notifier completion before rendered pixels. The remaining compute work is the staged-transfer
+fixed, X is reliable and the guest's real GL draws forward and execute on the
+physical GPU, so the remaining graphics gates are the beef GR ring
+resolution, the fixed-CB image's zero MVP block and the render-target bind
+before rendered pixels. The remaining compute work is the staged-transfer
class (under repair), the every-boot acceptance campaign, and per-guest
execution isolation — see
[`Execution-Frontier.md`](Execution-Frontier.md) and