[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190703135941.GL128603@google.com>
Date: Wed, 3 Jul 2019 08:59:41 -0500
From: Bjorn Helgaas <helgaas@...nel.org>
To: Alex Williamson <alex.williamson@...hat.com>
Cc: linux-pci@...r.kernel.org,
Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@...ux.intel.com>,
KarimAllah Ahmed <karahmed@...zon.de>,
Hao Zheng <yinhe@...ux.alibaba.com>,
linux-kernel@...r.kernel.org, nanhai.zou@...ux.alibaba.com,
quan.xu0@...ux.alibaba.com, ashok.raj@...el.com,
keith.busch@...el.com, mike.campin@...el.com
Subject: Re: [PATCH 0/2] PCI/IOV: Resolve regression in SR-IOV VF cfg_size
On Thu, Jun 13, 2019 at 04:56:57PM -0600, Alex Williamson wrote:
> The commit reverted in the first patch introduced a regression where
> only the first VF reports the correct config space size, subsequent VFs
> report 256 bytes of config space. Replace this in the second patch
> with an assumption that all VFs support extended config space by virtue
> of the SR-IOV spec requiring a PCIe capability and reachability of the
> PF extended config space already being proven by the existence of the
> VF. Thanks,
>
> Alex
>
> ---
>
> Alex Williamson (2):
> Revert: PCI/IOV: Use VF0 cached config space size for other VFs
> PCI/IOV: Assume SR-IOV VFs support extended config space.
Applied to pci/virtualization for v5.3 with Kuppuswamy's reviewed-by on
2/2, thanks!
> drivers/pci/iov.c | 2 --
> drivers/pci/pci.h | 1 -
> drivers/pci/probe.c | 26 ++++++++++++--------------
> 3 files changed, 12 insertions(+), 17 deletions(-)
Powered by blists - more mailing lists