diff options
Diffstat (limited to 'docs/03-architecture/07-driver-lifecycle-field-guide.md')
| -rw-r--r-- | docs/03-architecture/07-driver-lifecycle-field-guide.md | 15 |
1 files changed, 9 insertions, 6 deletions
diff --git a/docs/03-architecture/07-driver-lifecycle-field-guide.md b/docs/03-architecture/07-driver-lifecycle-field-guide.md index 9de5edb..1bfe912 100644 --- a/docs/03-architecture/07-driver-lifecycle-field-guide.md +++ b/docs/03-architecture/07-driver-lifecycle-field-guide.md @@ -105,7 +105,7 @@ fallback). Representative controls: | `0x20802a02` | CE PCE mask | one bit per engine | | `0x20802a08` | CE fault method buffer size | method buffer sizing | | `0x90f10106` | vaspace reserved-PDE contract | **carries page-table physical addresses** (see GSP-RM doc) | -| `0x20800123` / `0x20800170` | `GPU_GET_ENGINES` / `GET_ENGINES_V2` | engine inventory (filtered by the class list / classDB); values are consumed — the guest must see the full engine list, including the async copy engine (`COPY14`), and the current `rc=999` blocker lives here | +| `0x20800123` / `0x20800170` | `GPU_GET_ENGINES` / `GET_ENGINES_V2` | engine inventory (filtered by the class list / classDB); values are consumed — the guest must see the full engine list, including the async copy engine (`COPY14`); that inventory is now complete, and the context-creation wait lives later in the completion path | | `0x800201` | `GPU_GET_CLASSLIST` | class list (classDB); must agree with the engine list and the CE caps controls | | `0x2080012b` | GPU_PROMOTE_CTX (560-byte params) | issued immediately before context creation; fallback generic `SUCCESS`, consumed fields not yet coherent | | `0x20803039` | NVLink masks/VBIOS info | fallback: generic `SUCCESS` with zeroed params | @@ -166,13 +166,16 @@ their memsets, copies and semaphore releases in software by translating the semaphore VA to a guest physical address (see the UVM and host-module docs). This is a bridge, not forwarding: no work reaches the physical GPU yet. -**Live development front (2026-09-23):** CUDA context creation — `cuCtxCreate` -returns `rc=999` (`CUDA_ERROR_UNKNOWN`) because the emulated engine list lacks -the async copy engine (`COPY14`). The engine-record layout and the alloc -reply-fidelity checks are the first things to inspect +**Live development front (2026-09-29):** CUDA context creation — the client +reaches `cuCtxCreate` and currently ends in a forced `rc=999` on a completion +wait; the engine inventory is complete and the completion/translation path is +the focus. The engine-record layout and the alloc reply-fidelity checks are +documented in ([`../../userspace/cuda/docs/05-570.144-decompilation.md` §3.3/§3.6](../../userspace/cuda/docs/05-570.144-decompilation.md); start at -[`../../userspace/cuda/READ-ME-FIRST.md`](../../userspace/cuda/READ-ME-FIRST.md)). +[`../../userspace/cuda/READ-ME-FIRST.md`](../../userspace/cuda/READ-ME-FIRST.md)); +the execution backend is in +[`08-physical-gpu-integration.md`](08-physical-gpu-integration.md). **Log signatures (guest side):** ``` |