iommu.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
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.13-rc3
Date: Fri, 4 Aug 2017 10:38:54 +0200	[thread overview]
Message-ID: <20170804083849.GA15959@8bytes.org> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2241 bytes --]

Hi Linus,

The following changes since commit 520eccdfe187591a51ea9ab4c1a024ae4d0f68d9:

  Linux 4.13-rc2 (2017-07-23 16:15:17 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git tags/iommu-fixes-v4.13-rc3

for you to fetch changes up to 74ddda71f44c84af62f736a77fb9fcebe5bb436a:

  iommu/amd: Fix schedule-while-atomic BUG in initialization code (2017-07-26 15:39:14 +0200)

----------------------------------------------------------------
IOMMU Fixes for Linux v4.13-rc3

Including:

	- Fix a scheduling-while-atomic bug in the AMD IOMMU driver. It
	  was found after the checker was enabled earlier.

	- A fix for the virtual APIC code in the AMD IOMMU driver which
	  delivers device interrupts directly into KVM guests for
	  assigned devices.

	- Fixes for the recently merged lock-less page-table code for
	  ARM. The redundant TLB syncs got reverted and locks added
	  again around the TLB sync code.

	- Fix for error handling in arm_smmu_add_device()

	- Address sanitization fix for arm io-pgtable code

----------------------------------------------------------------
Joerg Roedel (2):
      Merge branch 'for-joerg/arm-smmu/fixes' of git://git.kernel.org/.../will/linux into iommu/fixes
      iommu/amd: Fix schedule-while-atomic BUG in initialization code

Robin Murphy (3):
      iommu/mtk: Avoid redundant TLB syncs locally
      Revert "iommu/io-pgtable: Avoid redundant TLB syncs"
      iommu/io-pgtable: Sanitise map/unmap addresses

Suravee Suthikulpanit (1):
      iommu/amd: Enable ga_log_intr when enabling guest_mode

Vivek Gautam (1):
      iommu/arm-smmu: Fix the error path in arm_smmu_add_device

Will Deacon (1):
      iommu/arm-smmu: Reintroduce locking around TLB sync operations

 drivers/iommu/amd_iommu.c          |  1 +
 drivers/iommu/amd_iommu_init.c     |  2 +-
 drivers/iommu/arm-smmu.c           | 18 +++++++++++++-----
 drivers/iommu/io-pgtable-arm-v7s.c |  6 ++++++
 drivers/iommu/io-pgtable-arm.c     |  7 +++++++
 drivers/iommu/io-pgtable.h         |  9 +--------
 drivers/iommu/mtk_iommu.c          |  6 ++++++
 drivers/iommu/mtk_iommu.h          |  1 +
 8 files changed, 36 insertions(+), 14 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:[~2017-08-04  8: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=20170804083849.GA15959@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).