diff options
Diffstat (limited to 'docs/05-operations/01-performance-correctness-security.md')
| -rw-r--r-- | docs/05-operations/01-performance-correctness-security.md | 21 |
1 files changed, 18 insertions, 3 deletions
diff --git a/docs/05-operations/01-performance-correctness-security.md b/docs/05-operations/01-performance-correctness-security.md index c4d8153..0a27709 100644 --- a/docs/05-operations/01-performance-correctness-security.md +++ b/docs/05-operations/01-performance-correctness-security.md @@ -17,6 +17,19 @@ Rung 4 SUSTAINED workloads run for hours; faults/errors recoverable Rung 5 MULTI-TENANT N VMs, isolation + fairness + no cross-talk ``` +**Current rung (2026-09-23):** Rung 1 is green; **Rung 2 is NOT green.** +`cuInit`/`cuDeviceGet` succeed, but `cuCtxCreate` returns `rc=999` +(`CUDA_ERROR_UNKNOWN`) because the emulated engine list lacks the async copy +engine (`COPY14`); `cuMemAlloc` is not reached and teardown of the failed +context still oopses in the guest kernel. Before Rung 3 is claimed, the +**reply-fidelity gate** applies: a control whose reply fields the driver +consumes is not implemented until the reply is coherent (status-only → +coherent zeroed params → coherent values for consumed fields → exact values) — +see +[`../../userspace/cuda/docs/04-virtualization-and-emulation.md` §6](../../userspace/cuda/docs/04-virtualization-and-emulation.md). +New to CUDA analysis here: start at +[`../../userspace/cuda/READ-ME-FIRST.md`](../../userspace/cuda/READ-ME-FIRST.md). + ## 2. Correctness ### 2.1 Test corpus @@ -47,9 +60,11 @@ Rung 5 MULTI-TENANT N VMs, isolation + fairness + no cross-talk ### 2.3 Regression gates -`make test` runs the host suite. The CI ladder runs the guest suite on a -scheduled cadence and on every release. A rung regression is a release blocker; -the handoff documents carry the current rung. +`./scripts/stack_manager.sh test` runs the host suite (`make tests` only builds +the test binaries). CI (`.github/workflows/ci.yml`) runs on push and pull +requests only — there is currently no scheduled guest suite and no +stock-driver contract test. A rung regression is a release blocker; the +handoff documents carry the current rung. ## 3. Performance |