summaryrefslogtreecommitdiffstats
path: root/wiki/open-iov.org/index.php/File:Ioeventfd-and-irqfd.png.html
diff options
context:
space:
mode:
authorArthur Hanson Rasmusson <arthur@vgpu.io>2026-11-12 09:26:28 -0500
committerArthur Hanson Rasmusson <arthur@vgpu.io>2026-11-12 09:26:28 -0500
commit6260daa1eb66094e86a1d02128b97708242074e8 (patch)
treedcaec1cead67ffb8d1eb87a36a7157974b1ab00e /wiki/open-iov.org/index.php/File:Ioeventfd-and-irqfd.png.html
parent91aa8d91b54a2f9393d9582925464948b673601d (diff)
downloadopen-iov-6260daa1eb66094e86a1d02128b97708242074e8.tar.gz
open-iov-6260daa1eb66094e86a1d02128b97708242074e8.zip
docs: vGPU bring-up size/state traps (FB units, GART, modeNum parity)
Record the three independent guest-visible values that broke stock-driver bring-up: FB info kilobyte-vs-byte units (1024x framebuffer over-report), multi-GiB GPU GART allocation, and odd shared nvClip modeNum (clears the GL client's init bits so buffer maps fail). Each has a different diagnostic signature; the note separates allocation-size, userspace mapping-gate, and host VAS-translation failures. Evidence: c15-c26 bring-up, commits 8c7bf295/d1dc85a2/91aa8d91 and handoff-meta-plan.md CONT.435-CONT.441.
Diffstat (limited to 'wiki/open-iov.org/index.php/File:Ioeventfd-and-irqfd.png.html')
0 files changed, 0 insertions, 0 deletions