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.7-rc5
Date: Fri, 1 Jul 2016 17:36:24 +0200	[thread overview]
Message-ID: <20160701153611.GA28903@8bytes.org> (raw)


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

Hi Linus,

The following changes since commit a4c34ff1c029e90e7d5f8dd8d29b0a93b31c3cb2:

  iommu/vt-d: Enable QI on all IOMMUs before setting root entry (2016-06-17 11:29:48 +0200)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git tags/iommu-fixes-v4.7-rc5

for you to fetch changes up to 6082ee72e9d89e80a664418be06f47d728243e85:

  iommu/amd: Initialize devid variable before using it (2016-06-27 13:24:46 +0200)

----------------------------------------------------------------
IOMMU Fixes for Linux v4.7-rc5

Three fixes:

	* Fix use of smp_processor_id() in preemptible code in the IOVA
	  allocation code. This got introduced with the scalability
	  improvements in this release cycle.

	* A VT-d fix for out-of-bounds access of the iommu->domains
	  array. The bug showed during suspend/resume.

	* AMD IOMMU fix to print the correct device id in the ACPI
	  parsing code.

----------------------------------------------------------------
Chris Wilson (1):
      iommu/iova: Disable preemption around use of this_cpu_ptr()

Jan Niehusmann (1):
      iommu/vt-d: Fix overflow of iommu->domains array

Nicolas Iooss (1):
      iommu/amd: Initialize devid variable before using it

 drivers/iommu/amd_iommu_init.c | 2 +-
 drivers/iommu/intel-iommu.c    | 2 +-
 drivers/iommu/iova.c           | 8 ++++++--
 3 files changed, 8 insertions(+), 4 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-07-01 15:36 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=20160701153611.GA28903@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).