summaryrefslogtreecommitdiffstats
path: root/docs/01-orientation/01-purpose-and-scope.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/01-orientation/01-purpose-and-scope.md')
-rw-r--r--docs/01-orientation/01-purpose-and-scope.md19
1 files changed, 10 insertions, 9 deletions
diff --git a/docs/01-orientation/01-purpose-and-scope.md b/docs/01-orientation/01-purpose-and-scope.md
index ff13603..278ad0d 100644
--- a/docs/01-orientation/01-purpose-and-scope.md
+++ b/docs/01-orientation/01-purpose-and-scope.md
@@ -131,15 +131,16 @@ 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 CUDA user-space
- startup through `cuInit` / `cuDeviceGet`.
-* **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
+ probe and enumerate, guest `nvidia.ko` and `nvidia-smi`, and the full CUDA
+ driver-API path through context creation, allocation and verified copies
+ (the driver-API smoke passes).
+* **Needs improvement**: engine execution first — the backend is live and
+ CE-class copies and their releases are forwarded to the physical copy engine
+ (default off) with a fault relay, but CUDA kernel execution is blocked on GR
+ engine-context validity — then the remaining reply fidelity (some consumed
+ fields are still generic fallbacks), 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).