diff options
| author | Arthur Hanson Rasmusson <arthur@vgpu.io> | 2026-10-06 15:18:39 -0400 |
|---|---|---|
| committer | Arthur Hanson Rasmusson <arthur@vgpu.io> | 2026-10-06 15:18:39 -0400 |
| commit | 6b0673a21b1cb5493554c898181fe289355cadc0 (patch) | |
| tree | bc684bb7e4a9897de2530304f3946c9da00ee941 /docs/05-operations | |
| parent | af5489f9473cedb146d5a9269d19195e03396d02 (diff) | |
| download | open-iov-6b0673a21b1cb5493554c898181fe289355cadc0.tar.gz open-iov-6b0673a21b1cb5493554c898181fe289355cadc0.zip | |
docs: add the GR compute-launch frontier page and align execution status across the tree
New page docs/04-implementation/03-execution-frontier.md describes the chain
that must fire for a guest CUDA launch (guest push -> GPFIFO/front-end ->
inline launch-descriptor install -> engine read/dispatch -> completion),
where the leading edge is (the descriptor install path), how we know
(front-end vs engine-authored observables and their limits), what is
exonerated (context validity at dispatch, destination window mapping,
fetch alignment, shared-buffer rule, parenting), the ranked issues (verbatim
prelude targets, missing descriptor-virtualization control, sentinel
hygiene), live investigation lines and labelled theories.
Align every page that still said GR execution is blocked on engine-context
validity to the current frontier, and add the new page to the README reading
order (row 15, later rows renumbered). Docs only; no code.
Diffstat (limited to 'docs/05-operations')
| -rw-r--r-- | docs/05-operations/01-performance-correctness-security.md | 8 |
1 files changed, 6 insertions, 2 deletions
diff --git a/docs/05-operations/01-performance-correctness-security.md b/docs/05-operations/01-performance-correctness-security.md index 21afd06..2f10b35 100644 --- a/docs/05-operations/01-performance-correctness-security.md +++ b/docs/05-operations/01-performance-correctness-security.md @@ -22,8 +22,12 @@ Rung 5 MULTI-TENANT N VMs, isolation + fairness + no cross-talk (`ALL OK` 64/64, copies matched) — `cuInit`, device queries, context creation, allocation, copies, free and destroy complete, and the copies are verified byte-for-byte. **Rung 3 is partial:** CE-class copies execute on the physical -copy engine (default off) with engine-authored releases and a fault relay, but -CUDA kernel execution is blocked on GR engine-context validity. Before Rung 3 +copy engine (default off) with engine-authored releases and a fault relay; for +GR kernel execution a forwarded guest launch now reaches the front-end but the +inline launch-descriptor install has not been observed (no grid dispatched; +context validity at dispatch is ruled out — +[`../04-implementation/03-execution-frontier.md`](../04-implementation/03-execution-frontier.md)). +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 → |