diff options
Diffstat (limited to 'docs/05-operations/01-performance-correctness-security.md')
| -rw-r--r-- | docs/05-operations/01-performance-correctness-security.md | 11 |
1 files changed, 6 insertions, 5 deletions
diff --git a/docs/05-operations/01-performance-correctness-security.md b/docs/05-operations/01-performance-correctness-security.md index 583d6c8..3a2c6b4 100644 --- a/docs/05-operations/01-performance-correctness-security.md +++ b/docs/05-operations/01-performance-correctness-security.md @@ -17,11 +17,12 @@ 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 +**Current rung (2026-09-29):** Rung 1 is green; **Rung 2 is in progress.** +`cuInit`/`cuDeviceGet` succeed, and the client reaches `cuCtxCreate`, which +currently ends in a forced `rc=999` on a completion wait (engine inventory +complete; completion translation in progress); `cuMemAlloc` is not reached yet +and failed-context teardown has oopsed in the guest kernel in earlier runs. +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) — |