Currently, we use pcie_flags_reg to cache PCI-E Capabilities Register,
because PCI-E Capabilities Register bits are almost read-only. This patch
use pcie_flags_reg instead of another access PCI-E Capabilities Register.

Signed-off-by: Yijing Wang <wangyij...@huawei.com>
---
 drivers/vfio/pci/vfio_pci_config.c |    6 +-----
 1 files changed, 1 insertions(+), 5 deletions(-)

diff --git a/drivers/vfio/pci/vfio_pci_config.c 
b/drivers/vfio/pci/vfio_pci_config.c
index aeb00fc..afc6ca4 100644
--- a/drivers/vfio/pci/vfio_pci_config.c
+++ b/drivers/vfio/pci/vfio_pci_config.c
@@ -1017,13 +1017,9 @@ static int vfio_cap_len(struct vfio_pci_device *vdev, u8 
cap, u8 pos)
                return byte;
        case PCI_CAP_ID_EXP:
                /* length based on version */
-               ret = pci_read_config_word(pdev, pos + PCI_EXP_FLAGS, &word);
-               if (ret)
-                       return pcibios_err_to_errno(ret);
-
                vdev->extended_caps = true;
 
-               if ((word & PCI_EXP_FLAGS_VERS) == 1)
+               if ((pdev->pcie_flags_reg & PCI_EXP_FLAGS_VERS) == 1)
                        return PCI_CAP_EXP_ENDPOINT_SIZEOF_V1;
                else
                        return PCI_CAP_EXP_ENDPOINT_SIZEOF_V2;
-- 
1.7.1


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to