From: Alex Williamson <alex.williamson@redhat.com>
To: linux-pci@vger.kernel.org
Cc: Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@linux.intel.com>,
KarimAllah Ahmed <karahmed@amazon.de>,
Hao Zheng <yinhe@linux.alibaba.com>,
bhelgaas@google.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: [PATCH 0/2] PCI/IOV: Resolve regression in SR-IOV VF cfg_size
Date: Thu, 13 Jun 2019 16:56:57 -0600 [thread overview]
Message-ID: <156046609596.29869.5839964168034189416.stgit@gimli.home> (raw)
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.
drivers/pci/iov.c | 2 --
drivers/pci/pci.h | 1 -
drivers/pci/probe.c | 26 ++++++++++++--------------
3 files changed, 12 insertions(+), 17 deletions(-)
next reply other threads:[~2019-06-13 22:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 22:56 Alex Williamson [this message]
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 ` [PATCH 0/2] PCI/IOV: Resolve regression in SR-IOV VF cfg_size Bjorn Helgaas
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=156046609596.29869.5839964168034189416.stgit@gimli.home \
--to=alex.williamson@redhat.com \
--cc=ashok.raj@intel.com \
--cc=bhelgaas@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).