From: Alex Williamson <alex.williamson-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: bhelgaas-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org
Cc: linux-pci-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org
Subject: [RFC PATCH 0/2] pci/iommu: PCIe requester ID interface
Date: Wed, 10 Jul 2013 16:10:32 -0600 [thread overview]
Message-ID: <20130710215954.3045.89568.stgit@bling.home> (raw)
I took Bjorn's requester ID interface, or more appropriately my
interpretation of the interface, through a full (apparently) working
implementation. This is the result. It's quite a nice cleanup for
intel-iommu. I think this kills two birds with one stone, we quirk
PCIe-to-PCI bridges that don't have a PCIe capability (bz44881) and we
also apply DMA quirks to all devices for dma_ops, which should fix
devices like Ricoh and Marvell chips that do DMA from the wrong
requester ID (still no ghost requester ID support, but that may be
easier to add now).
If this seems like the right direction I'll update other users of
pci_find_upstream_pcie_bridge() and abolish that function. Thanks,
Alex
---
Alex Williamson (2):
pci: Create PCIe requester ID interface
iommu/intel: Make use of PCIe requester ID interface
drivers/iommu/intel-iommu.c | 164 ++++++++++++++++-------------------------
drivers/pci/search.c | 170 +++++++++++++++++++++++++++++++++++++++++++
include/linux/pci.h | 7 ++
next reply other threads:[~2013-07-10 22:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-10 22:10 Alex Williamson [this message]
[not found] ` <20130710215954.3045.89568.stgit-xdHQ/5r00wBBDLzU/O5InQ@public.gmane.org>
2013-07-10 22:10 ` [RFC PATCH 1/2] pci: Create PCIe requester ID interface Alex Williamson
2013-07-10 22:10 ` [RFC PATCH 2/2] iommu/intel: Make use of " 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=20130710215954.3045.89568.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 \
/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).