https://bugzilla.kernel.org/show_bug.cgi?id=202055 Alex Williamson (alex.williamson@xxxxxxxxxx) changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alex.williamson@xxxxxxxxxx --- Comment #1 from Alex Williamson (alex.williamson@xxxxxxxxxx) --- There's been another report[1] that this devices reports an invalid MSI-X capability where the vector table and PBA do overlap. The user there reports: Capabilities: [b0] MSI-X: Enable- Count=22 Masked- Vector table: BAR=0 offset=00002000 PBA: BAR=0 offset=00002100 Where each vector table entry is 16 bytes therefore a 22 entry vector table based at 0x2000 would extend to at least 0x2160 but the PBA is claimed to start at 0x2100. We have different results here: Capabilities: [b0] MSI-X: Enable+ Count=16 Masked- Vector table: BAR=0 offset=00002000 PBA: BAR=0 offset=00002100 It appears that this capability is sane and should pass the QEMU sanity test, but clearly it did not, so did this capability report the same values when vfio read it? Note that in the first case MSI-X is not enabled while in the latter case it is enabled and we can see the device is bound to the nvme driver. Perhaps this suggests there are states where this device reports a valid MSI-X capability and states where it does not. I would suggest: a) Unbind the device from the nvme driver, bind it to vfio-pci, look at lspci in the host and see if the Count value in the MSI-X capability has changed. b) If the device still reports Count=16 after the steps in a), continue from that point by resetting the device via pci-sysfs (ex. echo 1 > /sys/bus/pci/devices/0000:06:00.0/reset). Look again at lspci in the host to see if the Count value has changed. Thanks [1]https://patchwork.kernel.org/patch/10707761/ -- You are receiving this mail because: You are watching the assignee of the bug.
