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/03-architecture/11-physical-backend-guest-wiring.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/03-architecture/11-physical-backend-guest-wiring.md')
| -rw-r--r-- | docs/03-architecture/11-physical-backend-guest-wiring.md | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/docs/03-architecture/11-physical-backend-guest-wiring.md b/docs/03-architecture/11-physical-backend-guest-wiring.md index 943dd44..22d06ed 100644 --- a/docs/03-architecture/11-physical-backend-guest-wiring.md +++ b/docs/03-architecture/11-physical-backend-guest-wiring.md @@ -27,6 +27,14 @@ > forwarded-engine fault relay is live green, default off. The P6a trigger > residual is fixed: triggers 6/7 re-translate at trigger time and use fresh > scratch lines. +> +> **Update (2026-10-06): the frontier has moved.** A forwarded guest CUDA +> launch now reaches the front-end (ring entry fetched, methods executed) but +> the inline launch-descriptor (QMD) install has not been observed and no grid +> has dispatched; context validity at dispatch is ruled out. The current wall +> is the form of the forwarded launch method stream — the chain, evidence and +> live investigation lines are in +> [`../04-implementation/03-execution-frontier.md`](../04-implementation/03-execution-frontier.md). > The physical backend itself is live: the module-owned > GSP-RM completes initialization on the real TU104, serves the full > static-config reply, and shuts down gracefully. The host resource-manager |