From 1fdbf4ea8c17dab2b8fca6b5e58c2a6d3bc7596d Mon Sep 17 00:00:00 2001 From: Arthur Hanson Rasmusson Date: Tue, 29 Sep 2026 15:29:00 -0400 Subject: docs: record physical-GPU integration mechanism and refresh project status - add docs/03-architecture/08-physical-gpu-integration.md: interfaces that exist, mechanism options A-E, chosen path (module-owned GPU driven through its real GSP firmware), sharing policy, decision record - update 06-host-module-and-hybrid-model, 02-practical-challenges, system overview, known-knowns, docs/README reading order and CUDA-side docs to match - correct stale engine-topology/COPY14 blocker claims across the tree - add STATE-CURRENT.md as the dated public status snapshot --- docs/05-operations/01-performance-correctness-security.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) (limited to 'docs/05-operations/01-performance-correctness-security.md') 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) — -- cgit v1.2.3