summaryrefslogtreecommitdiffstats
path: root/docs/01-orientation
diff options
context:
space:
mode:
authorArthur Hanson Rasmusson <arthur@vgpu.io>2026-09-29 15:29:00 -0400
committerArthur Hanson Rasmusson <arthur@vgpu.io>2026-09-29 15:29:00 -0400
commit4738b619c45abc4cf98a549c3118839e48bb7244 (patch)
treecb6004f1a6351edbc482031189d359fd2882dab5 /docs/01-orientation
parent8d45a99fe54cb2b19b3024fd975ab11574611c3e (diff)
downloadopen-iov-4738b619c45abc4cf98a549c3118839e48bb7244.tar.gz
open-iov-4738b619c45abc4cf98a549c3118839e48bb7244.zip
docs: record physical-GPU integration mechanism and refresh project status
- add docs/03-architecture/08-physical-gpu-integration.md: interfaces that exist, mechanism options A-E, chosen path (module-owned GPU driven through its real GSP firmware), sharing policy, decision record - update 06-host-module-and-hybrid-model, 02-practical-challenges, system overview, known-knowns, docs/README reading order and CUDA-side docs to match - correct stale engine-topology/COPY14 blocker claims across the tree - add STATE-CURRENT.md as the dated public status snapshot
Diffstat (limited to 'docs/01-orientation')
-rw-r--r--docs/01-orientation/01-purpose-and-scope.md10
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/01-orientation/01-purpose-and-scope.md b/docs/01-orientation/01-purpose-and-scope.md
index c1232f3..ff13603 100644
--- a/docs/01-orientation/01-purpose-and-scope.md
+++ b/docs/01-orientation/01-purpose-and-scope.md
@@ -133,11 +133,11 @@ document:
transport, the resource-manager emulation surface the guest driver needs to
probe and enumerate, guest `nvidia.ko` and `nvidia-smi`, and CUDA user-space
startup through `cuInit` / `cuDeviceGet`.
-* **Needs improvement**: engine topology and reply fidelity first — context
- creation returns `rc=999` (`CUDA_ERROR_UNKNOWN`) because the emulated engine
- list lacks the async copy engine (`COPY14`) and some consumed reply fields
- are still generic fallbacks — then GPU work forwarding (the reason CUDA
- kernels do not yet run), the memory/page-table model, Windows guest support,
+* **Needs improvement**: reply fidelity and completion translation first —
+ context creation currently ends in a forced `rc=999` on a completion wait,
+ and some consumed reply fields are still generic fallbacks — then GPU work
+ forwarding (the reason CUDA kernels do not yet run; the backend is chosen),
+ the memory/page-table model, Windows guest support,
non-KVM hypervisors, and performance instrumentation. Each of these is
tracked with explicit "known-unknowns" in
[`../04-implementation/01-known-knowns-and-unknowns.md`](../04-implementation/01-known-knowns-and-unknowns.md);