On Tue, Nov 11, 2025 at 11:26:43AM -0800, David Matlack wrote:
On Tue, Nov 11, 2025 at 10:48 AM Alex Mastro amastro@fb.com wrote:
Changes in v3:
- Update capability chain cycle detection
- Clarify the iova=vaddr commit message
- Link to v2: https://lore.kernel.org/r/20251111-iova-ranges-v2-0-0fa267ff9b78@fb.com
All tests are still passing on v3 for me.
Hey David, is vfio_pci_driver_test known to be in good shape? Both on the base commit and after my series, I am seeing below, which results in a KSFT_SKIP. Invoking other tests in a similar way actually runs things with expected results (my devices are already bound to vfio-pci before running anything).
base commit: 0ed3a30fd996cb0cac872432cf25185fda7e5316
$ vfio_pci_driver_test -f 0000:05:00.0 No driver found for device 0000:05:00.0
Same thing using the run.sh wrapper
$ sudo ./run.sh -d 0000:05:00.0 ./vfio_pci_driver_test + echo "0000:05:00.0" > /sys/bus/pci/drivers/vfio-pci/unbind + echo "vfio-pci" > /sys/bus/pci/devices/0000:05:00.0/driver_override + echo "0000:05:00.0" > /sys/bus/pci/drivers/vfio-pci/bind
No driver found for device 0000:05:00.0 + echo "0000:05:00.0" > /sys/bus/pci/drivers/vfio-pci/unbind + echo "" > /sys/bus/pci/devices/0000:05:00.0/driver_override + echo "0000:05:00.0" > /sys/bus/pci/drivers/vfio-pci/bind
device = vfio_pci_device_init(device_bdf, default_iommu_mode); if (!device->driver.ops) { fprintf(stderr, "No driver found for device %s\n", device_bdf); return KSFT_SKIP; }
Is this meant to be a placeholder for some future testing, or am I holding things wrong?