From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: Linus Torvalds
<torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [git pull] IOMMU Updates for v3.11
Date: Mon, 8 Jul 2013 10:02:18 +0200 [thread overview]
Message-ID: <20130708080204.GA3289@8bytes.org> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 3029 bytes --]
Hi Linus,
The following changes since commit 9e895ace5d82df8929b16f58e9f515f6d54ab82d:
Linux 3.10-rc7 (2013-06-22 09:47:31 -1000)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git tags/iommu-updates-v3.11
for you to fetch changes up to 01ce784acfa69a171afe6ec3f85a959546f2d18a:
Merge branches 'x86/vt-d', 'arm/omap', 'core', 'x86/amd' and 'arm/smmu' into next (2013-06-25 23:34:29 +0200)
----------------------------------------------------------------
IOMMU Updates for Linux 3.11
A few updates this time, most important and exiciting (to me) is:
* The new ARM SMMU driver. This is a common IOMMU driver that will
hopefully be used in a lot of upcoming ARM chips. So the mess in the
past where every SOC had its own IOMMU will be over.
Besides that:
* Some important fixes in the IOMMU unmap path. There are fixes in the
common code and also in the AMD IOMMU driver.
* Other random fixes
----------------------------------------------------------------
Alex Williamson (4):
iommu/{vt-d,amd}: Remove multifunction assumption around grouping
iommu: Split iommu_unmaps
iommu: Fix compiler warning on pr_debug
iommu/amd: Only unmap large pages from the first pte
Andy Lutomirski (1):
iommu/vt-d: Downgrade the warning if enabling irq remapping fails
Joe Perches (1):
iommu: Use %pa and %zx instead of casting
Joerg Roedel (2):
iommu/amd: Fix memory leak in free_pagetable
Merge branches 'x86/vt-d', 'arm/omap', 'core', 'x86/amd' and 'arm/smmu' into next
Li, Zhen-Hua (1):
iommu/vt-d: DMAR reporting table needs at least one DRHD
Suman Anna (2):
iommu/omap: fix printk formats for dma_addr_t
iommu/omap: fix checkpatch warnings in omap iommu code
Will Deacon (3):
documentation/iommu: Add description of ARM System MMU binding
iommu/arm: Add support for ARM Ltd. System MMU architecture
MAINTAINERS: add entry for ARM system MMU driver
.../devicetree/bindings/iommu/arm,smmu.txt | 70 +
MAINTAINERS | 6 +
drivers/iommu/Kconfig | 13 +
drivers/iommu/Makefile | 1 +
drivers/iommu/amd_iommu.c | 104 +-
drivers/iommu/arm-smmu.c | 1969 ++++++++++++++++++++
drivers/iommu/dmar.c | 4 +
drivers/iommu/intel-iommu.c | 25 +-
drivers/iommu/intel_irq_remapping.c | 3 +-
drivers/iommu/iommu.c | 86 +-
drivers/iommu/omap-iommu.c | 15 +-
drivers/iommu/omap-iopgtable.h | 2 +-
drivers/iommu/omap-iovmm.c | 4 +-
13 files changed, 2212 insertions(+), 90 deletions(-)
create mode 100644 Documentation/devicetree/bindings/iommu/arm,smmu.txt
create mode 100644 drivers/iommu/arm-smmu.c
Please pull.
Thanks,
Joerg
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
reply other threads:[~2013-07-08 8:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20130708080204.GA3289@8bytes.org \
--to=joro-zlv9swrftaidnm+yrofe0a@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@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).