iommu.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: bhelgaas-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org,
	stephen-OTpzqLSitTUnbdJkjeBofR2eb7JE58TQ@public.gmane.org
Cc: linux-pci-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
	dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org
Subject: [PATCH 0/3] pci/iommu: Quirk non-compliant PCIe-to-PCI bridges
Date: Fri, 10 May 2013 15:18:39 -0600	[thread overview]
Message-ID: <20130510210937.32592.21950.stgit@bling.home> (raw)

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 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.

This works on my VT-d system, but I don't have any of the offending
bridges.  Appreciate testing from those who do.  I'll link this series
to the bz above for more testing.  Thanks,

Alex

---

Alex Williamson (3):
      pci: Add PCI walk function and PCIe bridge test
      intel-iommu: Convert to pci_walk_up_to_first_match
      pci: Remove pci_find_pcie_upstream_bridge


 drivers/iommu/intel-iommu.c         |   77 ++++++++++++++++++++++-------------
 drivers/iommu/intel_irq_remapping.c |   13 ++++--
 drivers/pci/search.c                |   74 ++++++++++++++++++++++------------
 include/linux/pci.h                 |   26 +++++++++---
 4 files changed, 124 insertions(+), 66 deletions(-)

             reply	other threads:[~2013-05-10 21:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-10 21:18 Alex Williamson [this message]
     [not found] ` <20130510210937.32592.21950.stgit-xdHQ/5r00wBBDLzU/O5InQ@public.gmane.org>
2013-05-10 21:18   ` [PATCH 1/3] pci: Add PCI walk function and PCIe bridge test Alex Williamson
2013-05-13 13:51     ` Sethi Varun-B16395
     [not found]       ` <C5ECD7A89D1DC44195F34B25E172658D50609A-RL0Hj/+nBVCMXPU/2EZmt64g8xLGJsHaLnY5E4hWTkheoWH0uzbU5w@public.gmane.org>
2013-05-13 14:49         ` Alex Williamson
2013-05-22 14:34           ` Sethi Varun-B16395
     [not found]             ` <C5ECD7A89D1DC44195F34B25E172658D544C52-RL0Hj/+nBVDYdknt8GnhQq4g8xLGJsHaLnY5E4hWTkheoWH0uzbU5w@public.gmane.org>
2013-05-22 15:02               ` Alex Williamson
2013-05-23 20:44     ` Bjorn Helgaas
2013-05-10 21:18   ` [PATCH 2/3] intel-iommu: Convert to pci_walk_up_to_first_match Alex Williamson
2013-05-10 21:18   ` [PATCH 3/3] pci: Remove pci_find_pcie_upstream_bridge 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=20130510210937.32592.21950.stgit@bling.home \
    --to=alex.williamson-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=bhelgaas-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
    --cc=dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
    --cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=linux-pci-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=stephen-OTpzqLSitTUnbdJkjeBofR2eb7JE58TQ@public.gmane.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).