diff options
Diffstat (limited to 'docs/03-architecture/01-system-overview.md')
| -rw-r--r-- | docs/03-architecture/01-system-overview.md | 12 |
1 files changed, 7 insertions, 5 deletions
diff --git a/docs/03-architecture/01-system-overview.md b/docs/03-architecture/01-system-overview.md index 5c2ba6c..fa328ae 100644 --- a/docs/03-architecture/01-system-overview.md +++ b/docs/03-architecture/01-system-overview.md @@ -60,7 +60,7 @@ HOST MODULE open-iov-vfio.ko ├─ virtual device: config space, BAR0/BAR1/BAR3 windows, MSI-X ├─ emulation core: GSP boot + GSP-RM (RPC msgq, controls, objects, events) ├─ memory model: guest RAM access, VA↔PA maps, VRAM backing - └─ work path: channel/push forwarding to the physical GPU [goal; software bridge today] + └─ work path: channel/push forwarding to the physical GPU [CE copies forwarded (default off); GR open] │ module-owned device + real GSP session HOST BACKEND the GPU's own hardware + GSP firmware, driven by this module │ (the distribution nvidia.ko stays unmodified and unbound in @@ -170,10 +170,12 @@ decompiled and mapped (see `wiki/GSP-570.144W-Firmware-Analysis.md` and without server-side object management. Where the driver consumes a reply value, that value is still being corrected (the reply-fidelity ladder). 5. `nvidia-smi -L` enumerates the emulated device and CUDA user-space starts - (`cuInit` / `cuDeviceGetCount` / `cuDeviceGet` succeed). The client reaches - `cuCtxCreate`, which currently ends in a forced `rc=999` on a completion - wait; the copy-engine method streams execute in software as a bridge, and - the execution backend is not built yet (see + (`cuInit` / `cuDeviceGetCount` / `cuDeviceGet` succeed); context creation + completes and the full CUDA driver-API smoke passes (`ALL OK` 64/64, copies + matched). The execution backend is live: CE-class copies are + forwarded to the physical copy engine (default off) with engine-authored + semaphore releases and a fault relay; kernel execution is blocked on GR + engine-context validity (see [`08-physical-gpu-integration.md`](08-physical-gpu-integration.md)). The CUDA-side contract and the reply-fidelity rules are documented in |