summaryrefslogtreecommitdiffstats
path: root/userspace/cuda/docs/07-version-upgrade-playbook.md
diff options
context:
space:
mode:
authorArthur Hanson Rasmusson <arthur@vgpu.io>2026-09-23 12:26:03 -0400
committerArthur Hanson Rasmusson <arthur@vgpu.io>2026-09-23 12:26:03 -0400
commit71c1a2147681127209453a811b918d66d8eebbad (patch)
tree14dfebfbabd347aed9161d9e9cf0115d8725c2c2 /userspace/cuda/docs/07-version-upgrade-playbook.md
parent692c095ae48f2829613873e60e4dbbf14b36323d (diff)
downloadopen-iov-71c1a2147681127209453a811b918d66d8eebbad.tar.gz
open-iov-71c1a2147681127209453a811b918d66d8eebbad.zip
kernel: service BAR0/BAR1 region reads and extended config-space writes
Two more retry loops surfaced once the guest driver got past the CE binding: - BAR0 region reads returned -EINVAL ("would be handled by mmap"), so a QEMU-trapped read of BAR0+0x88084 failed and the driver polled it forever. Serve reads from the BAR0 shadow/trap handler (and mirror BAR1 reads from the emulated vidmem backing). - Config-space writes above offset 0xFF were refused with -EINVAL, so the driver's write to extended config 0x704 (PCIe device control area) never took effect and it retried. Accept and store extended-space writes; keep the legacy identity registers fixed.
Diffstat (limited to 'userspace/cuda/docs/07-version-upgrade-playbook.md')
0 files changed, 0 insertions, 0 deletions