open-iov.git/docs, branch lottery-m156-gate-attemptOpen-IOV vGPU-IO: host-side GSP emulation for unmodified NVIDIA guest drivers
https://git.vgpu.io/open-iov.git/atom?h=lottery-m156-gate-attempt2026-10-08T18:10:23+00:00docs(review): fix GMMU-doc anchors and vEP vocabulary; index docs 13/14 in the READMEs2026-10-08T18:10:23+00:00Arthur Hanson Rasmussonarthur@vgpu.io2026-10-08T18:10:23+00:00urn:sha1:94352c708442be843950e17e3613dce539ca9fdb
The GMMU doc cited pre-a9d29cba lines for the pump, doorbell and svc_sem_write,
defined vEP differently from doc 13 (which it names as the vocabulary
authority), and called Design A prototypable in the 1.0 programme while M6
classifies the same prototype as post-1.0 research. Fix all three, refresh
the status hash, and add the doc to the docs/ and wiki/ indexes with the
renumbered reading-order rows.
docs(review): refresh vEP citations against merged master and reconcile GR completion with FORENSICS-grv52026-10-08T18:10:21+00:00Arthur Hanson Rasmussonarthur@vgpu.io2026-10-08T18:10:21+00:00urn:sha1:236e63726c9a99e220d43475aa89ed8c06d719ef
Line anchors drifted when a9d29cba landed after the doc was written at
0da66259 (svc_thread, svc_gr_request, svc_pending_add, the H3 guard, the
readiness gate). Also: the grv5 SEMA_DBG=Y campaign showed the notifier and
event wake-up do fire while the counter slot publication is the link that
never writes, so the document's 'completion wake-up' framing was stale in
the stage table, section 3.4, section 6.1, the challenges and the iteration
plan; refresh the status hash, the discovery-cadence wording and the
mode-matrix source note, and extend the change log.
Merge branches 'docs/vexecution-plane' and 'docs/multi-tenant-gmmu'2026-10-08T18:04:47+00:00Arthur Hanson Rasmussonarthur@vgpu.io2026-10-08T18:04:47+00:00urn:sha1:c8ec65aeff12fb6b8bdc2c5028d247f1af6e6fe7docs(multi-tenant-gmmu): multi-mdev isolation design, GMMU tenant/agent paged-attention protection, VRAM oversubscription, portability and M1-M8 roadmap (wiki summary; local provenance in adjacent LOCAL notes)2026-10-08T17:51:22+00:00Arthur Hanson Rasmussonarthur@vgpu.io2026-10-08T17:51:22+00:00urn:sha1:dc551a6bf1458f6a9d621ce97bd86607e38b1080docs(vexecution-plane): add the vGSP Execution Plane architecture doc, wiki deep dive and indexes2026-10-08T17:41:31+00:00Arthur Hanson Rasmussonarthur@vgpu.io2026-10-08T17:41:31+00:00urn:sha1:b7c5212f7691f71202a7c3661993354132429712docs/07: state the actual userspace C style; record de facto conventions2026-10-08T15:52:59+00:00Arthur Hanson Rasmussonarthur@vgpu.io2026-10-08T15:52:59+00:00urn:sha1:e95b4055edbc160e64e2561e32debb220303cf41
Section 3.2 documented 'same style as the kernel module where practical',
which the sources contradicted (4-space indentation throughout). It now
states the real rules: 4-space/~100-col C, snake_case/_t naming, include
guards, status-type error handling, existing set -e/pipefail and SPDX
practice. New section 3.4 records conventions that were only implicit:
commit-message format with ISSUE-0001 refs, doc Status/change markers,
config/ and firmware/ layout, and the per-file SPDX enforcement point.
risc-v-gsp-rm-debugger: land docs 45-53 + harness/sim tool set with tests2026-10-06T23:28:39+00:00Arthur Hanson Rasmussonarthur@vgpu.io2026-10-06T23:28:39+00:00urn:sha1:cd1f2528e8243fed3ce80d5170ef93928e4e7284
rm_capture (chunked decode), launch_audit, state_seed/state_decode,
valprobe, rehost, contracts+run_contracts, host_traffic, gmmu_walk,
msgq_attach, libos_port, log_decode, server_snapshot; doc index updates
in the tool overview, operations pages and the repo README.
docs: 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:6b0673a21b1cb5493554c898181fe289355cadc0
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.
docs: draw the physical-backend lifecycle (init, work, completion, teardown) on one page2026-10-06T00:08:06+00:00Arthur Hanson Rasmussonarthur@vgpu.io2026-10-06T00:08:06+00:00urn:sha1:0ffde4d41eb43e69d8ba7b19780dcf51a8210eb1docs: record GR rung-2 ctx-query ABI fix and the managed-booking wall2026-10-05T18:02:51+00:00Arthur Hanson Rasmussonarthur@vgpu.io2026-10-05T18:02:51+00:00urn:sha1:2a308ccd0786736693ef4369d387de33a0fe6447
Document the corrected GR context-buffer query ABI (80-byte entries, 5136
byte params), the new gsp_phys_rmcall_srv_ctxcommit / gsp_phys_rmcall_channel
/ gsp_phys_gr_forward parameters, and the live 2026-10-05 findings: PA-only
never commits the engine context pointer; on the shared VAS the server
pre-books MAIN as managed so a client VA-only promote returns 0x40 at the
vaListSetManaged gate; EVICT_CTX does not release it; the external-VAS
VA-promote shape wedged the device and must not be repeated.