summaryrefslogtreecommitdiffstats
path: root/docs/03-architecture/09-full-system-picture.md
diff options
context:
space:
mode:
authorArthur Hanson Rasmusson <arthur@vgpu.io>2026-10-01 00:06:19 -0400
committerArthur Hanson Rasmusson <arthur@vgpu.io>2026-10-01 00:06:19 -0400
commit97a389906065337e2dbccef658965441067df104 (patch)
treee18648875dbe588b61cfda167e95a5ee8f794fb0 /docs/03-architecture/09-full-system-picture.md
parentb4526594948b15b16326f0e4807b155a83b258a5 (diff)
downloadopen-iov-97a389906065337e2dbccef658965441067df104.tar.gz
open-iov-97a389906065337e2dbccef658965441067df104.zip
docs: refresh status wording after the 64/64 baseline and the physical-backend lock
Diffstat (limited to 'docs/03-architecture/09-full-system-picture.md')
-rw-r--r--docs/03-architecture/09-full-system-picture.md8
1 files changed, 7 insertions, 1 deletions
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