summaryrefslogtreecommitdiffstats
path: root/wiki/open-iov.org/index.php?title=Introduction&action=info.html
diff options
context:
space:
mode:
authorArthur Hanson Rasmusson <arthur@vgpu.io>2026-10-06 15:18:39 -0400
committerArthur Hanson Rasmusson <arthur@vgpu.io>2026-10-06 15:18:39 -0400
commit6b0673a21b1cb5493554c898181fe289355cadc0 (patch)
treebc684bb7e4a9897de2530304f3946c9da00ee941 /wiki/open-iov.org/index.php?title=Introduction&action=info.html
parentaf5489f9473cedb146d5a9269d19195e03396d02 (diff)
downloadopen-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 'wiki/open-iov.org/index.php?title=Introduction&action=info.html')
0 files changed, 0 insertions, 0 deletions