From: Alex Williamson <alex.williamson@hp.com>
To: dwmw2@infradead.org
Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org, alex.williamson@hp.com
Subject: [PATCH 0/5] intel-iommu fixes
Date: Mon, 26 Oct 2009 17:24:53 -0600 [thread overview]
Message-ID: <20091026232401.9646.90540.stgit@nehalem.aw> (raw)
This series implements several fixes for intel-iommu. The first
is to make use of the device coherent_dma_mask when allocating
coherent DMA buffers, for which we move dma_generic_alloc_coherent
out of the x86 code so we can use it by both of the current users
of intel-iommu. Next, we add a little more to detecting when a
device can't support passthrough mode. Then we reinstate RMRRs
for devices that get kicked out of passthrough mode. And finally,
a trivial printk change to be less verbose on boot.
Ideally I'd like to entertain the idea of getting these into 2.6.32
because the coherent mapping issue is actually a regression since
2.6.31 and will cause some devices to fail to initialize in passthrough
mode (cciss for one). Thanks,
Alex
---
Alex Williamson (5):
intel-iommu: Quiet unnecessary output
intel-iommu: Reinstate RMRRs if a device is removed from passthrough domain
intel-iommu: Use max_pfn to determine whether a device can passthrough
intel-iommu: Use dma_generic_alloc_coherent() for passthrough mappings
dma: create dma_generic_alloc/free_coherent()
arch/x86/include/asm/dma-mapping.h | 3 --
arch/x86/kernel/pci-dma.c | 31 --------------------
arch/x86/kernel/pci-nommu.c | 10 +++++--
drivers/pci/intel-iommu.c | 55 +++++++++++++++++++++++++++++++++---
include/linux/dma-mapping.h | 44 +++++++++++++++++++++++++++++
5 files changed, 102 insertions(+), 41 deletions(-)
next reply other threads:[~2009-10-26 23:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 23:24 Alex Williamson [this message]
2009-10-26 23:24 ` [PATCH 1/5] dma: create dma_generic_alloc/free_coherent() Alex Williamson
2009-10-27 0:57 ` Paul Mundt
2009-10-27 2:26 ` Alex Williamson
2009-10-27 1:47 ` FUJITA Tomonori
2009-10-26 23:25 ` [PATCH 2/5] intel-iommu: Use dma_generic_alloc_coherent() for passthrough mappings Alex Williamson
2009-10-27 3:24 ` [PATCH v2 2/5] intel-iommu: Obey coherent_dma_mask for alloc_coherent on passthrough Alex Williamson
2009-10-26 23:25 ` [PATCH 3/5] intel-iommu: Use max_pfn to determine whether a device can passthrough Alex Williamson
2009-10-26 23:25 ` [PATCH 4/5] intel-iommu: Reinstate RMRRs if a device is removed from passthrough domain Alex Williamson
2009-10-27 8:15 ` David Woodhouse
2009-10-27 15:50 ` Alex Williamson
2009-10-28 14:36 ` David Woodhouse
2009-10-28 16:06 ` Alex Williamson
2009-10-28 20:35 ` Alex Williamson
2009-10-26 23:25 ` [PATCH 5/5] intel-iommu: Quiet unnecessary output 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=20091026232401.9646.90540.stgit@nehalem.aw \
--to=alex.williamson@hp.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox