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 Fixes for Linux v4.7-rc3
Date: Fri, 17 Jun 2016 16:38:58 +0200 [thread overview]
Message-ID: <20160617143845.GA25478@8bytes.org> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1467 bytes --]
Hi Linus,
The following changes since commit 5edb56491d4812c42175980759da53388e5d86f5:
Linux 4.7-rc3 (2016-06-12 07:20:35 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git tags/iommu-fixes-v4.7-rc3
for you to fetch changes up to a4c34ff1c029e90e7d5f8dd8d29b0a93b31c3cb2:
iommu/vt-d: Enable QI on all IOMMUs before setting root entry (2016-06-17 11:29:48 +0200)
----------------------------------------------------------------
IOMMU Fixes for Linux v4.7-rc3
Three patches queued up:
* Fix for ARM-SMMU to add a missing iommu-ops callback which is
required by common iommu code
* Fix for the rockchip iommu where the wrong MMUs got the
commands
* A regression fix for the Intel VT-d driver. The regression
only showed up on X58 chipsets with more than one iommu. These
chipsets seem to require that QI is enabled on all IOMMUs
before it can be used.
----------------------------------------------------------------
Jean-Philippe Brucker (1):
iommu/arm-smmu: Wire up map_sg for arm-smmu-v3
Joerg Roedel (1):
iommu/vt-d: Enable QI on all IOMMUs before setting root entry
John Keeping (1):
iommu/rockchip: Fix zap cache during device attach
drivers/iommu/arm-smmu-v3.c | 1 +
drivers/iommu/intel-iommu.c | 17 ++++++++++++-----
drivers/iommu/rockchip-iommu.c | 2 +-
3 files changed, 14 insertions(+), 6 deletions(-)
Please pull.
Thanks,
Joerg
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
reply other threads:[~2016-06-17 14:38 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=20160617143845.GA25478@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).