From: "Sean O. Stalley" <sean.stalley@intel.com>
To: linux-pci@vger.kernel.org, mj@ucw.cz, bhelgaas@google.com,
alex.williamson@redhat.com
Cc: sean.stalley@intel.com, david.daney@cavium.com
Subject: [PATCH v4 0/2] pci/lspci: Identify Enhanced Allocation (EA) Resources
Date: Thu, 11 Feb 2016 16:52:23 -0800 [thread overview]
Message-ID: <1455238345-5602-1-git-send-email-sean.stalley@intel.com> (raw)
Identify BAR-equivalent resources that are described by EA entries
with the IORESOURCE_PCI_EA_BEI flag.
lspci cannot distinguish between resources from VF BARs and resources from EA.
This results in EA Resources being incorrectly identified as [virtual].
Adding this flag allows EA resources to be marked more accurately as [enhanced].
Although this patchset only add support for this flag to lspci,
there are other use cases (such as vfio) where knowing a resource
comes from EA would be useful.
[PATCH 1/2] is for the kernel, [PATCH 2/2] is for lspci.
Changes from V1:
-Rewrote commit message for linux changes
Changes from V2:
- Rewrote commit message for linux, fixing spelling :)
- Added warning about resource flags being exposed in sysfs
Changes from V3 (only lspci changes):
- Incremented libpci API version number
- append new flag variables to the end of struct pci_dev (so we don't break binary compatiblity)
- expanded comment for the resource flags
- removed brackets around 1 line conditionals
Alex Williamson (1):
pci: Identify Enhanced Allocation (EA) BAR Equivalent resources
Sean O. Stalley (1):
Add support for enhanced allocation regions
linux changes:
drivers/pci/pci.c | 2 +-
include/linux/ioport.h | 7 +++++++
2 files changed, 8 insertions(+), 1 deletion(-)
lspci changes:
lib/access.c | 18 ++++++++++--------
lib/caps.c | 2 +-
lib/filter.c | 2 +-
lib/header.h | 4 ++++
lib/libpci.ver | 5 +++++
lib/pci.h | 3 +++
lib/sysfs.c | 7 +++++--
lspci.c | 12 +++++++++---
8 files changed, 38 insertions(+), 15 deletions(-)
--
1.9.1
next reply other threads:[~2016-02-12 0:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 0:52 Sean O. Stalley [this message]
2016-02-12 0:52 ` [PATCH v4 1/2] pci: Identify Enhanced Allocation (EA) BAR Equivalent resources Sean O. Stalley
2016-05-16 20:31 ` Bjorn Helgaas
2016-05-16 22:07 ` Stalley, Sean
2016-02-12 0:52 ` [PATCH v4 2/2] Add support for enhanced allocation regions Sean O. Stalley
2016-04-10 22:22 ` Bjorn Helgaas
2016-05-14 9:28 ` Martin Mares
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=1455238345-5602-1-git-send-email-sean.stalley@intel.com \
--to=sean.stalley@intel.com \
--cc=alex.williamson@redhat.com \
--cc=bhelgaas@google.com \
--cc=david.daney@cavium.com \
--cc=linux-pci@vger.kernel.org \
--cc=mj@ucw.cz \
/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).