diff options
Diffstat (limited to 'docs/03-architecture')
| -rw-r--r-- | docs/03-architecture/06-host-module-and-hybrid-model.md | 2 | ||||
| -rw-r--r-- | docs/03-architecture/09-full-system-picture.md | 8 |
2 files changed, 8 insertions, 2 deletions
diff --git a/docs/03-architecture/06-host-module-and-hybrid-model.md b/docs/03-architecture/06-host-module-and-hybrid-model.md index e29951c..d6b96e7 100644 --- a/docs/03-architecture/06-host-module-and-hybrid-model.md +++ b/docs/03-architecture/06-host-module-and-hybrid-model.md @@ -314,6 +314,6 @@ in `kernel-open` first). | Push decoding + semaphore completion | demonstrated live; being productized | | Page-table population for server-owned ranges | designed, not implemented | | GPU work forwarding (GR/CE execution) | designed, not implemented | -| Execution backend (module-owned GPU + direct real-GSP session) | chosen, not started ([`08-physical-gpu-integration.md`](08-physical-gpu-integration.md)) | +| Execution backend (module-owned GPU + direct real-GSP session) | mechanism chosen; ownership + firmware staging verified live; power-domain lock implemented, pending supervised verification; real GSP boot not started ([`08-physical-gpu-integration.md`](08-physical-gpu-integration.md)) | | Real VRAM backing | designed, not implemented | | Windows guest, Xen transport, aarch64 hosts | designed, not implemented | diff --git a/docs/03-architecture/09-full-system-picture.md b/docs/03-architecture/09-full-system-picture.md index 0df0dd2..e03a68e 100644 --- a/docs/03-architecture/09-full-system-picture.md +++ b/docs/03-architecture/09-full-system-picture.md @@ -91,7 +91,13 @@ that device and the physical engines is either emulated (control plane) or translated (work plane) by one kernel module, with no daemon, no host userspace and no modified driver on either side. The distribution `nvidia.ko` remains installed and unmodified on the host; it is simply unbound from the GPU while -the service owns it, and the host's display runs on another GPU. +the service owns it, and the host's display runs on another GPU. Unbinding is +not a neutral operation on every platform — the board's power domain can +power-gate the GPU and hard-freeze the host — so ownership must hold a D0 lock +over the GPU, its board companions and the root port across the whole +unbind/rebind window; the hazard and the lock are described in +[`08-physical-gpu-integration.md`](08-physical-gpu-integration.md) §4.2, and the +driver must never be unbound without the lock. ## 2. The control plane: GSP emulation |