summaryrefslogtreecommitdiffstats
path: root/wiki/Host-Module.md
diff options
context:
space:
mode:
Diffstat (limited to 'wiki/Host-Module.md')
-rw-r--r--wiki/Host-Module.md18
1 files changed, 10 insertions, 8 deletions
diff --git a/wiki/Host-Module.md b/wiki/Host-Module.md
index 35bf3c8..6405874 100644
--- a/wiki/Host-Module.md
+++ b/wiki/Host-Module.md
@@ -6,7 +6,7 @@
> source: [`../docs/03-architecture/06-host-module-and-hybrid-model.md`](../docs/03-architecture/06-host-module-and-hybrid-model.md);
> the docs tree wins on disagreement with this page.
>
-> Status: 2026-11-09, tree `master @ 21e0d611`. Tags: `[live]` observed with
+> Status: 2026-11-09, tree `master @ cb8e822b`. Tags: `[live]` observed with
> the stock guest driver; `[wip]` demonstrated live, being productized;
> `[gated]` implemented default-off behind supervised gates; `[wall]` known
> blocking limit; `[target]` designed, not built; `[planned]` roadmap.
@@ -107,9 +107,11 @@ from kernel context**, so the module **owns the device and runs its real GSP
firmware as the resource-manager server**, with emulation as the control
plane. CE copies, release and fault relay are implemented default-off and
verified live [gated]; forwarded guest CUDA launches execute on the engine
-with engine-authored completions relayed to the guest, and graphics method
-streams execute in three shapes, including the direct GL client's own GR/CE
-channels ([`Execution-Frontier.md`](Execution-Frontier.md),
+with engine-authored completions relayed to the guest; the guest's real GL
+draws now forward and execute on the physical GR engine (`work_gr
+backend_ok=9`), and graphics method streams execute in three shapes,
+including the direct GL client's own GR/CE channels
+([`Execution-Frontier.md`](Execution-Frontier.md),
[`Graphics-Execution.md`](Graphics-Execution.md)).
The same plane carries the display/modeset path [live in the campaign
@@ -122,10 +124,10 @@ nvidia-modeset/NvKms register (`/dev/dri`), X settle and GLX clients obtain a
real GL context. The display-capability seam is parameterised. For the DDX's
own 2D push buffers the remaining host levers are publishing/advancing the
GPU-written engine get word and recycling the notifier to `0xffff` after
-completion. For a windowed GL client the host must also make the kick
-completion visible to the guest kernel and signal its modeset event: writing
-the beef notifier memory alone leaves `poll()` on the per-slot
-`/dev/nvidia-modeset` fd waiting.
+completion. For a windowed GL client the GSP event-IRQ path raises the
+RISC-V SWGEN0 interrupt and latches the CPU-tree leaf so the guest services
+the event and completes swaps; the remaining GL gap is the constant-buffer
+(MVP) page (the draw writes 0 pages) and the MME/wedge stability.
## 6. Debug parameters