From: Bjorn Helgaas <helgaas@kernel.org>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: linux-pci@vger.kernel.org,
Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@linux.intel.com>,
KarimAllah Ahmed <karahmed@amazon.de>,
Hao Zheng <yinhe@linux.alibaba.com>,
linux-kernel@vger.kernel.org, nanhai.zou@linux.alibaba.com,
quan.xu0@linux.alibaba.com, ashok.raj@intel.com,
keith.busch@intel.com, mike.campin@intel.com
Subject: Re: [PATCH 0/2] PCI/IOV: Resolve regression in SR-IOV VF cfg_size
Date: Wed, 3 Jul 2019 08:59:41 -0500 [thread overview]
Message-ID: <20190703135941.GL128603@google.com> (raw)
In-Reply-To: <156046609596.29869.5839964168034189416.stgit@gimli.home>
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(-)
prev parent reply other threads:[~2019-07-03 13:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 22:56 [PATCH 0/2] PCI/IOV: Resolve regression in SR-IOV VF cfg_size Alex Williamson
2019-06-13 22:57 ` [PATCH 1/2] Revert: PCI/IOV: Use VF0 cached config space size for other VFs Alex Williamson
2019-06-13 22:57 ` [PATCH 2/2] PCI/IOV: Assume SR-IOV VFs support extended config space Alex Williamson
2019-06-19 19:54 ` sathyanarayanan kuppuswamy
2019-07-03 13:59 ` Bjorn Helgaas [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190703135941.GL128603@google.com \
--to=helgaas@kernel.org \
--cc=alex.williamson@redhat.com \
--cc=ashok.raj@intel.com \
--cc=karahmed@amazon.de \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mike.campin@intel.com \
--cc=nanhai.zou@linux.alibaba.com \
--cc=quan.xu0@linux.alibaba.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=yinhe@linux.alibaba.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.