summaryrefslogtreecommitdiffstats
path: root/docs/05-operations/02-debugging-and-maintenance-workflows.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/05-operations/02-debugging-and-maintenance-workflows.md')
-rw-r--r--docs/05-operations/02-debugging-and-maintenance-workflows.md12
1 files changed, 5 insertions, 7 deletions
diff --git a/docs/05-operations/02-debugging-and-maintenance-workflows.md b/docs/05-operations/02-debugging-and-maintenance-workflows.md
index 52cee94..801cda6 100644
--- a/docs/05-operations/02-debugging-and-maintenance-workflows.md
+++ b/docs/05-operations/02-debugging-and-maintenance-workflows.md
@@ -136,13 +136,11 @@ userspace/cuda/tools/callwalk.py <elf-index>/callgraph.tsv callers 0xNNNNNN
* **A/B harness**: `tools/cuda-ab/` runs one deterministic CUDA workload on
bare metal and in the guest and diffs the stable result lines.
-**Known current bugs (2026-09-23)**: `cuCtxCreate` returns `rc=999`
-(`CUDA_ERROR_UNKNOWN`) because the emulated engine list is missing the async
-copy engine `COPY14`; the guest kernel oopses in
-`uvm_pmm_devmem_page_to_va_space` on teardown of the failed context; and
-control `0x2080012b` (560-byte params, issued immediately before context
-creation) is answered with a generic SUCCESS whose consumed fields are not yet
-coherent. Start at
+**Current frontier (2026-10-12)**: context creation and the full driver-API
+smoke pass (`ALL OK`, 64-byte payload round-trips); a guest CUDA kernel
+launch is forwarded but the engine does not execute the forwarded launch
+descriptor yet, and green runs are not reproducible on every boot (tracked as
+an open issue in the repository). Start at
[`../../userspace/cuda/READ-ME-FIRST.md`](../../userspace/cuda/READ-ME-FIRST.md),
[`../../userspace/cuda/docs/03-driver-and-gpu-interface.md`](../../userspace/cuda/docs/03-driver-and-gpu-interface.md)
and