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/03-architecture/02-guest-stack-and-cudasw.md | |
| 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/03-architecture/02-guest-stack-and-cudasw.md')
| -rw-r--r-- | docs/03-architecture/02-guest-stack-and-cudasw.md | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/docs/03-architecture/02-guest-stack-and-cudasw.md b/docs/03-architecture/02-guest-stack-and-cudasw.md index f9fe249..845e00f 100644 --- a/docs/03-architecture/02-guest-stack-and-cudasw.md +++ b/docs/03-architecture/02-guest-stack-and-cudasw.md @@ -95,8 +95,10 @@ module-owned GPU running its real GSP firmware as the resource-manager server (see [`../../userspace/cuda/docs/08-virtualization-approaches.md`](../../userspace/cuda/docs/08-virtualization-approaches.md) and [`08-physical-gpu-integration.md`](08-physical-gpu-integration.md)) — with -CE-class copies forwarded to the physical copy engine (default off) and GR -kernel execution blocked on GR engine-context validity. +CE-class copies forwarded to the physical copy engine (default off); for GR, a +forwarded guest launch reaches the front-end but 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)). For the CUDA userspace side of this stack — its architecture, how it is built and executes, and the exact kernel/GPU interface contract we must satisfy — |