open-iov.git/docs/04-implementation/03-execution-frontier.md, branch m32Open-IOV vGPU-IO: host-side GSP emulation for unmodified NVIDIA guest drivers
https://git.vgpu.io/open-iov.git/atom?h=m322026-10-06T19:18:39+00:00docs: add the GR compute-launch frontier page and align execution status across the tree2026-10-06T19:18:39+00:00Arthur Hanson Rasmussonarthur@vgpu.io2026-10-06T19:18:39+00:00urn:sha1:929646875d80408a21c642ca88ef70efbc0d736a
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.