diff options
| author | Arthur Hanson Rasmusson <arthur@vgpu.io> | 2026-10-08 14:10:23 -0400 |
|---|---|---|
| committer | Arthur Hanson Rasmusson <arthur@vgpu.io> | 2026-10-08 14:10:23 -0400 |
| commit | 0ced423a01e85b98fe0d6db7bf7c75300c900316 (patch) | |
| tree | d8d8300c5c317f04d6b95e95f758eeb0169d86f5 /wiki | |
| parent | 92e45de48d2465594d4619be11b28581020e9eea (diff) | |
| download | open-iov-0ced423a01e85b98fe0d6db7bf7c75300c900316.tar.gz open-iov-0ced423a01e85b98fe0d6db7bf7c75300c900316.zip | |
docs(review): fix GMMU-doc anchors and vEP vocabulary; index docs 13/14 in the READMEs
The GMMU doc cited pre-c33f6006 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.
Diffstat (limited to 'wiki')
| -rw-r--r-- | wiki/GMMU-Multi-Tenant-Protection.md | 6 | ||||
| -rw-r--r-- | wiki/README.md | 1 |
2 files changed, 4 insertions, 3 deletions
diff --git a/wiki/GMMU-Multi-Tenant-Protection.md b/wiki/GMMU-Multi-Tenant-Protection.md index 83b00ba..6ea5b9b 100644 --- a/wiki/GMMU-Multi-Tenant-Protection.md +++ b/wiki/GMMU-Multi-Tenant-Protection.md @@ -15,7 +15,7 @@ two halves: 1. **Service-state ownership (baseline 1.0).** The work/completion service (`kernel/gsp_sema_service.c`) is one global context (`static struct sema_svc svc`, `:676`), the pump services the first open mdev - (`:13296-13308`), and channels/VA spaces/translations are keyed by + (`:13352-13364`), and channels/VA spaces/translations are keyed by guest-chosen values alone (`:847`, `:988`, `:113-130`). Two guests can pick the same handles and VAs (live: channel `0xcaf000d4`; `../debug/issue/issue-number-2.md`), so owner-keying is a prerequisite @@ -76,12 +76,12 @@ periodic owner-vs-PTE audit with canaries catches escapes. If only per-tenant separation exists, the deployable contract is **one agent per tenant, one tenant per context** (canonical ยง5.4). -## Key code anchors (master `66388560`) +## Key code anchors (master `1f571dda`) | What | Where | |---|---| | per-mdev emulation context | `kernel/include/nvidia-vgpu-vfio.h:133`, `kernel/gsp_emulation.h:130` | -| global service state | `kernel/gsp_sema_service.c:676`; pump `:13296`; doorbell `:13456` | +| global service state | `kernel/gsp_sema_service.c:676`; pump `:13352`; doorbell `:13512` | | channel/vaspace registries | `kernel/gsp_sema_service.c:847`, `:988` | | GMMU walk (VER2) | `kernel/gsp_sema_service.c:1174`; decode `:1093` | | page directory record | `kernel/gsp_rm_emulation.c:3320`; reserved PDEs `:2237-2262` | diff --git a/wiki/README.md b/wiki/README.md index 378ea31..d04f70f 100644 --- a/wiki/README.md +++ b/wiki/README.md @@ -10,6 +10,7 @@ ### Core Analysis - [The vGSP Execution Plane (vEP)](Execution-Plane.md) - The work/execution layer of `vgsp.ko`: guest pushes to physical execution and guest-visible completion (condensed; canonical doc [`../docs/03-architecture/13-vexecution-plane.md`](../docs/03-architecture/13-vexecution-plane.md)) +- [GMMU Multi-Tenant Protection](GMMU-Multi-Tenant-Protection.md) - Multi-mdev isolation design and paged-attention (vLLM) tenant/agent protection at the GMMU: service-state ownership, per-context page directories, VRAM oversubscription (condensed; canonical doc [`../docs/03-architecture/14-multi-tenant-gmmu-protection.md`](../docs/03-architecture/14-multi-tenant-gmmu-protection.md)) - [GSP 570.144W Firmware Analysis](GSP-570.144W-Firmware-Analysis.md) - Firmware decompilation and address record - [Address Reference](Address-Reference.md) - Firmware-side address tables - [CUDA Userspace Driver](CUDA-Userspace-Driver.md) - `libcuda.so` deep dive: layer model, guest interface, forwarding status, crash-path lesson and lookup tooling |