summaryrefslogtreecommitdiffstats
path: root/docs/VERSION_UPGRADE.md
diff options
context:
space:
mode:
authorArthur Hanson Rasmusson <arthur@vgpu.io>2026-09-23 12:11:10 -0400
committerArthur Hanson Rasmusson <arthur@vgpu.io>2026-09-23 12:11:10 -0400
commit692c095ae48f2829613873e60e4dbbf14b36323d (patch)
tree6e48fc539c7b02b3f30654f7d1703beffa974277 /docs/VERSION_UPGRADE.md
parentf874d709e5a45d63c8ee9ab6b0300195aa5d20a5 (diff)
downloadopen-iov-692c095ae48f2829613873e60e4dbbf14b36323d.tar.gz
open-iov-692c095ae48f2829613873e60e4dbbf14b36323d.zip
docs: refresh status, supersede stale material, link the CUDA analysis
* Status now matches the live state: guest driver probe and nvidia-smi work; cuInit/device queries work; cuCtxCreate returns 999 because the emulated engine list is missing the async copy engine (COPY14). The userspace libcuda segfault is recorded as solved, with its mechanism (an RM allocation reply must echo request parameters; zeroing them corrupted the caller's saved frame pointer). * Correct the emulation claims: only a subset of RM controls are special-cased; the rest return a success reply with zeroed parameters whose consumed fields are still being corrected; allocation replies are coherent but no server-side object model exists. * Add the eight-point emulation checklist and reply-fidelity ladder as explicit gates, documented in userspace/cuda and linked from the architecture, implementation and operations docs. * Fix operational errors: build/test commands, module load order, mdev type names, LFS references, debugfs claims, in-repo firmware claims, CI claims, portability matrix (guest status, config layout, userspace driver facts). * Mark historical material: one superseded banner per legacy document with a pointer to its replacement; STATE.md marked as a 2026-09-21 snapshot. * Wiki: fix the index, add status banners and in-place factual corrections (msgq transport vs legacy mailbox, BAR definitions, error statuses, migration, glossary), and note the archived 2023 imports.
Diffstat (limited to 'docs/VERSION_UPGRADE.md')
-rw-r--r--docs/VERSION_UPGRADE.md7
1 files changed, 7 insertions, 0 deletions
diff --git a/docs/VERSION_UPGRADE.md b/docs/VERSION_UPGRADE.md
index b9bd387..3fc5de4 100644
--- a/docs/VERSION_UPGRADE.md
+++ b/docs/VERSION_UPGRADE.md
@@ -1,5 +1,12 @@
# Open-IOV Version Upgrade Guide
+> **Status: superseded (historical).** Part of the pre-2026-09-23 docs; kept
+> as a record. Current entry point: [docs/README.md](README.md).
+> Version-upgrade replacements:
+> [06-portability/hardware-software-matrix.md](06-portability/hardware-software-matrix.md)
+> and
+> [05-operations/02-debugging-and-maintenance-workflows.md](05-operations/02-debugging-and-maintenance-workflows.md).
+
> How to support a new NVIDIA driver version (e.g. moving from 570.144 to a
> 610-series release) end-to-end: firmware acquisition → reverse engineering →
> config → host driver → guest validation. The goal is that a version bump is