diff options
Diffstat (limited to 'docs/01-orientation/01-purpose-and-scope.md')
| -rw-r--r-- | docs/01-orientation/01-purpose-and-scope.md | 19 |
1 files changed, 12 insertions, 7 deletions
diff --git a/docs/01-orientation/01-purpose-and-scope.md b/docs/01-orientation/01-purpose-and-scope.md index eab63bc..c1232f3 100644 --- a/docs/01-orientation/01-purpose-and-scope.md +++ b/docs/01-orientation/01-purpose-and-scope.md @@ -131,13 +131,18 @@ document: * **Working today**: the virtual device, the GSP boot handshake, the RPC transport, the resource-manager emulation surface the guest driver needs to - probe and enumerate, guest `nvidia.ko` and `nvidia-smi`, and the early UVM - initialization path. -* **Needs improvement**: GPU work forwarding (the reason CUDA kernels do not - yet run), 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). + 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, + 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); + for the CUDA analysis area, start at + [`../../userspace/cuda/READ-ME-FIRST.md`](../../userspace/cuda/READ-ME-FIRST.md). ## 8. Guiding principles |