Commit a7b4133d authored by Konrad Rzeszutek Wilk's avatar Konrad Rzeszutek Wilk Committed by Sasha Levin

xen/pciback: Check PF instead of VF for PCI_COMMAND_MEMORY

[ Upstream commit d52a2481 ]

commit 8d47065f upstream.

Commit 408fb0e5 (xen/pciback: Don't
allow MSI-X ops if PCI_COMMAND_MEMORY is not set) prevented enabling
MSI-X on passed-through virtual functions, because it checked the VF
for PCI_COMMAND_MEMORY but this is not a valid bit for VFs.

Instead, check the physical function for PCI_COMMAND_MEMORY.
Signed-off-by: default avatarKonrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Reviewed-by: default avatarJan Beulich <jbeulich@suse.com>
Signed-off-by: default avatarDavid Vrabel <david.vrabel@citrix.com>
Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Signed-off-by: default avatarSasha Levin <sasha.levin@oracle.com>
parent fda3e3e7
...@@ -212,8 +212,9 @@ int xen_pcibk_enable_msix(struct xen_pcibk_device *pdev, ...@@ -212,8 +212,9 @@ int xen_pcibk_enable_msix(struct xen_pcibk_device *pdev,
/* /*
* PCI_COMMAND_MEMORY must be enabled, otherwise we may not be able * PCI_COMMAND_MEMORY must be enabled, otherwise we may not be able
* to access the BARs where the MSI-X entries reside. * to access the BARs where the MSI-X entries reside.
* But VF devices are unique in which the PF needs to be checked.
*/ */
pci_read_config_word(dev, PCI_COMMAND, &cmd); pci_read_config_word(pci_physfn(dev), PCI_COMMAND, &cmd);
if (dev->msi_enabled || !(cmd & PCI_COMMAND_MEMORY)) if (dev->msi_enabled || !(cmd & PCI_COMMAND_MEMORY))
return -ENXIO; return -ENXIO;
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment