All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: bhelgaas@google.com
Cc: linux-pci@vger.kernel.org, joro@8bytes.org,
	andihartmann@01019freenet.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] pci: ACS fixes & quirks
Date: Mon, 08 Jul 2013 10:17:42 -0600	[thread overview]
Message-ID: <1373300262.2602.22.camel@ul30vt.home> (raw)
In-Reply-To: <20130627222159.16564.38166.stgit@bling.home>

Ping.  Comments?

On Thu, 2013-06-27 at 16:39 -0600, Alex Williamson wrote:
> v2:
> 
> Revised patch 1/ to match comments from Bjorn.  PCIe event collectors
> and PCIe-to-PCI bridges now indicate that they do not support ACS.
> I've reached out to try to get clarification on this, but I think it's
> reasonable to proceed with a conservative approach until then.  I also
> added PCI-to-PCIe bridges for the sake of being complete.  Also added
> more comments about the purpose and behavior of pci_acs_enabled().  If
> I've overlooked anything else that needs to be addressed, please let
> me know.
> 
> Patch 2/ had no comments, it's unchanged.
> 
> Patch 3/ is added.  This was sent as an RFC nearly a year ago and
> Joerg confirmed for us that these devices do not support p2p on AMD
> systems with AMD IOMMU.  We can't simply use iommu_present() to test
> for an IOMMU because it's setup just after we need this function.  
> Instead we test for the ACPI IVRS table that describes the IOMMU.  It
> would probably suffice to skip an actual AMD IOMMU check, but I don't
> want it to later come bite us if these ASICs get re-used, maybe with
> a different IOMMU, and don't make the same guarantees.
> 
> Joerg, I was also curious back when we investigated this patch if the
> same rules hold true for these other southbridge devices:
> 
> 1002:43a0 SB700/SB800/SB900 PCI to PCI bridge (PCIE port 0)
> 1002:43a1 SB700/SB800/SB900 PCI to PCI bridge (PCIE port 1)
> 1002:43a2 SB900 PCI to PCI bridge (PCIE port 2)
> 1002:43a3 SB900 PCI to PCI bridge (PCIE port 3)
> 
> If you remember or have contacts to poke, I'd be happy to follow-up
> with another patch to add them.  Thanks,
> 
> Alex
> 
> ---
> 
> Alex Williamson (3):
>       pci: Fix flaw in pci_acs_enabled()
>       pci: Differentiate ACS controllable from enabled
>       pci: ACS quirk for AMD southbridge
> 
> 
>  drivers/pci/pci.c    |   93 +++++++++++++++++++++++++++++++++++++++++---------
>  drivers/pci/quirks.c |   50 +++++++++++++++++++++++++++
>  2 files changed, 127 insertions(+), 16 deletions(-)




  parent reply	other threads:[~2013-07-08 16:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-27 22:39 [PATCH v2 0/3] pci: ACS fixes & quirks Alex Williamson
2013-06-27 22:39 ` [PATCH v2 1/3] pci: Fix flaw in pci_acs_enabled() Alex Williamson
2013-06-27 22:39 ` [PATCH v2 2/3] pci: Differentiate ACS controllable from enabled Alex Williamson
2013-06-27 22:40 ` [PATCH v2 3/3] pci: ACS quirk for AMD southbridge Alex Williamson
2013-07-08 16:17 ` Alex Williamson [this message]
2013-07-12  7:01   ` [PATCH v2 0/3] pci: ACS fixes & quirks Don Dutile
2013-07-23 15:47   ` Alex Williamson
2013-07-23 20:19 ` 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=1373300262.2602.22.camel@ul30vt.home \
    --to=alex.williamson@redhat.com \
    --cc=andihartmann@01019freenet.de \
    --cc=bhelgaas@google.com \
    --cc=joro@8bytes.org \
    --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 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.