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/01-orientation/01-purpose-and-scope.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/01-orientation/01-purpose-and-scope.md')
| -rw-r--r-- | docs/01-orientation/01-purpose-and-scope.md | 7 |
1 files changed, 5 insertions, 2 deletions
diff --git a/docs/01-orientation/01-purpose-and-scope.md b/docs/01-orientation/01-purpose-and-scope.md index 278ad0d..ef4b258 100644 --- a/docs/01-orientation/01-purpose-and-scope.md +++ b/docs/01-orientation/01-purpose-and-scope.md @@ -136,8 +136,11 @@ document: (the driver-API smoke passes). * **Needs improvement**: engine execution first — the backend is live and CE-class copies and their releases are forwarded to the physical copy engine - (default off) with a fault relay, but CUDA kernel execution is blocked on GR - engine-context validity — then the remaining reply fidelity (some consumed + (default off) with a fault relay, but for CUDA kernel execution the guest's + launch now reaches the front-end and the inline launch-descriptor install has + not been observed (context validity at dispatch is ruled out; see + [`../04-implementation/03-execution-frontier.md`](../04-implementation/03-execution-frontier.md)) + — then the remaining reply fidelity (some consumed fields are still generic fallbacks), the memory/page-table model, Windows guest support, non-KVM hypervisors, and performance instrumentation. Each of these is tracked with explicit "known-unknowns" in |