From: Alex Williamson <alex.williamson@redhat.com>
To: bhelgaas@google.com
Cc: linux-pci@vger.kernel.org, ddutile@redhat.com,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] pci: ACS check fixes
Date: Fri, 07 Jun 2013 10:34:35 -0600 [thread overview]
Message-ID: <20130607162732.7733.17758.stgit@bling.home> (raw)
After some further discussion, Don has come around to agreeing that
we cannot assume anything about devices which do not include an ACS
capability. Patch 1 of this series is therefore the same as sent
before. We have figured out though that some vendors are indicating
that they don't support peer-to-peer by providing an ACS capability
that is zero'd (ie. no capabilities). This makes sense as ACS is
largely for allowing control of peer-to-peer features and almost all
of the individual capabilities are optional for multifunction
devices that do not support peer-to-peer. This also simplifies our
flags filtering. I'm hoping we'll soon have some quirks for devices
that do not support peer-to-peer, but also do not provide an ACS
capability. Thanks,
Alex
---
Alex Williamson (2):
pci: Fix flaw in pci_acs_enabled()
pci: Differentiate ACS controllable from enabled
drivers/pci/pci.c | 68 +++++++++++++++++++++++++++++++++++++++++------------
1 file changed, 52 insertions(+), 16 deletions(-)
next reply other threads:[~2013-06-07 16:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 16:34 Alex Williamson [this message]
2013-06-07 16:34 ` [PATCH v2 1/2] pci: Fix flaw in pci_acs_enabled() Alex Williamson
2013-06-18 17:09 ` Bjorn Helgaas
2013-06-18 18:38 ` Alex Williamson
2013-06-18 22:10 ` Bjorn Helgaas
2013-06-18 22:47 ` Alex Williamson
2013-06-19 2:30 ` Bjorn Helgaas
2013-06-20 21:43 ` Alex Williamson
2013-06-24 17:27 ` Bjorn Helgaas
2013-06-07 16:34 ` [PATCH v2 2/2] pci: Differentiate ACS controllable from enabled Alex Williamson
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=20130607162732.7733.17758.stgit@bling.home \
--to=alex.williamson@redhat.com \
--cc=bhelgaas@google.com \
--cc=ddutile@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
/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).