diff options
| author | Arthur Hanson Rasmusson <arthur@vgpu.io> | 2026-09-23 12:26:03 -0400 |
|---|---|---|
| committer | Arthur Hanson Rasmusson <arthur@vgpu.io> | 2026-09-23 12:26:03 -0400 |
| commit | f7980444a921a0b5027e05a74f7535138e816a3d (patch) | |
| tree | 1c2f59c3fb9e8422c90f0f699d12e0330f17c5fb /userspace/cuda/READ-ME-FIRST.md | |
| parent | 13f46e60760cc0855484cc69de913ea34f55c24f (diff) | |
| download | open-iov-f7980444a921a0b5027e05a74f7535138e816a3d.tar.gz open-iov-f7980444a921a0b5027e05a74f7535138e816a3d.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/READ-ME-FIRST.md')
0 files changed, 0 insertions, 0 deletions
