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 | 929646875d80408a21c642ca88ef70efbc0d736a (patch) | |
| tree | deb2946cc4407e4edcc6e3b56f37420e321acf40 /docs/04-implementation/02-practical-challenges-and-adversarial-interop.md | |
| parent | 039daee13c5bac50919eff1ca26977ac49e37b06 (diff) | |
| download | open-iov-929646875d80408a21c642ca88ef70efbc0d736a.tar.gz open-iov-929646875d80408a21c642ca88ef70efbc0d736a.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/04-implementation/02-practical-challenges-and-adversarial-interop.md')
| -rw-r--r-- | docs/04-implementation/02-practical-challenges-and-adversarial-interop.md | 7 |
1 files changed, 5 insertions, 2 deletions
diff --git a/docs/04-implementation/02-practical-challenges-and-adversarial-interop.md b/docs/04-implementation/02-practical-challenges-and-adversarial-interop.md index 4b886b3..93245c4 100644 --- a/docs/04-implementation/02-practical-challenges-and-adversarial-interop.md +++ b/docs/04-implementation/02-practical-challenges-and-adversarial-interop.md @@ -56,8 +56,11 @@ without a methodology is not accepted in this project. physical GPU (see §3). CE-class copies and their semaphore releases are now forwarded to the physical copy engine (default off) with a host-side fault relay, and memsets/copies/releases the host decoder understands still run in - software as a fail-closed correctness bridge. No CUDA kernel is forwarded - yet: GR kernel execution is blocked on GR engine-context validity. + software as a fail-closed correctness bridge. GR (kernel) execution is the + open frontier: a forwarded guest launch reaches the front-end but the inline + launch-descriptor install has not been observed and no grid has dispatched + (context validity at dispatch is ruled out — see + [`03-execution-frontier.md`](03-execution-frontier.md)). ## 3. Forwarding: the options and the chosen mechanism |