From: Alex Williamson <alex.williamson@redhat.com>
To: iommu@lists.linux-foundation.org
Cc: dwmw2@infradead.org, joro@8bytes.org, stephen@networkplumber.org,
linux-pci@vger.kernel.org, ddutile@redhat.com
Subject: Re: [PATCH v2 0/2] iommu/intel: Quirk non-compliant PCIe-to-PCI bridges
Date: Mon, 08 Jul 2013 11:07:20 -0600 [thread overview]
Message-ID: <1373303240.2602.28.camel@ul30vt.home> (raw)
In-Reply-To: <20130528183527.3318.5365.stgit@bling.home>
Joerg,
Where do we stand on this series? You had a concern that the heuristic
used in patch 1/ could be dangerous. The suggestion for detecting the
issue was actually from Bjorn who replied with his rationale. Do you
want to go in the direction of a fixed whitelist or do you agree that
even if the heuristic breaks it provides better behavior than what we
have now? Thanks,
Alex
On Tue, 2013-05-28 at 12:40 -0600, Alex Williamson wrote:
> This series tries to address:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=44881
>
> Where pci_find_upstream_pcie_bridge() gets lost trying to find the
> upstream PCIe-to-PCI bridge for a device because the bridge doesn't
> expose a PCIe capability. To do this, we add a iommu_pci_is_pcie_bridge
> function which includes a quirk to look to the next upstream device
> as a sanity check. We can then replace pci_find_upstream_pcie_bridge
> with a function that's a bit more generic and less tied to intel-iommu
> eccentricities.
>
> v2 uses the same logic as v1, but moves the search and match code to
> IOMMU-core since PCI-core doesn't want it. v1 has several reports
> from users that this solves the problem they have in the above bz.
> Thanks,
>
> Alex
>
> ---
>
> Alex Williamson (2):
> iommu: Quirked PCIe bridge test and search function
> intel-iommu: Convert to iommu_pci_find_upstream + iommu_pci_is_pcie_bridge
>
>
> drivers/iommu/Kconfig | 5 ++
> drivers/iommu/Makefile | 1
> drivers/iommu/intel-iommu.c | 77 ++++++++++++++++++++++-------------
> drivers/iommu/intel_irq_remapping.c | 15 +++++--
> drivers/iommu/pci.c | 69 +++++++++++++++++++++++++++++++
> drivers/iommu/pci.h | 23 ++++++++++
> 6 files changed, 157 insertions(+), 33 deletions(-)
> create mode 100644 drivers/iommu/pci.c
next prev parent reply other threads:[~2013-07-08 17:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-28 18:40 [PATCH v2 0/2] iommu/intel: Quirk non-compliant PCIe-to-PCI bridges Alex Williamson
2013-05-28 18:40 ` [PATCH v2 1/2] iommu: Quirked PCIe bridge test and search function Alex Williamson
2013-05-28 19:38 ` Stephen Hemminger
2013-05-28 19:53 ` Alex Williamson
2013-05-28 19:56 ` Stephen Hemminger
2013-05-28 20:15 ` Alex Williamson
2013-05-28 20:28 ` Stephen Hemminger
2013-06-20 13:59 ` Joerg Roedel
2013-06-20 15:44 ` Alex Williamson
2013-06-20 16:15 ` Joerg Roedel
2013-06-26 4:20 ` Bjorn Helgaas
2013-06-26 18:45 ` Alex Williamson
2013-06-26 19:11 ` Bjorn Helgaas
2013-05-28 18:40 ` [PATCH v2 2/2] intel-iommu: Convert to iommu_pci_find_upstream + iommu_pci_is_pcie_bridge Alex Williamson
2013-05-28 22:09 ` [PATCH v2 0/2] iommu/intel: Quirk non-compliant PCIe-to-PCI bridges Bjorn Helgaas
2013-05-28 22:53 ` [PATCH v2 3/2] pci: Remove unused pci_find_upstream_pcie_bridge() Alex Williamson
2013-07-08 17:07 ` Alex Williamson [this message]
2013-07-08 19:34 ` [PATCH v2 0/2] iommu/intel: Quirk non-compliant PCIe-to-PCI bridges Bjorn Helgaas
2013-07-08 20:49 ` Alex Williamson
2013-07-08 21:51 ` Bjorn Helgaas
2013-07-09 18:27 ` Alex Williamson
2013-07-09 20:10 ` Bjorn Helgaas
2013-07-30 11:52 ` Joerg Roedel
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=1373303240.2602.28.camel@ul30vt.home \
--to=alex.williamson@redhat.com \
--cc=ddutile@redhat.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-pci@vger.kernel.org \
--cc=stephen@networkplumber.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).