All of lore.kernel.org
 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-rc6
Date: Fri, 8 Jul 2016 16:30:56 +0200	[thread overview]
Message-ID: <20160708143046.GA1093@8bytes.org> (raw)


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

Hi Linus,

The following changes since commit a99cde438de0c4c0cecc1d1af1a55a75b10bfdef:

  Linux 4.7-rc6 (2016-07-03 23:01:00 -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-rc6

for you to fetch changes up to 522e5cb76d0663c88f96b6a8301451c8efa37207:

  iommu/amd: Fix unity mapping initialization race (2016-07-06 18:04:55 +0200)

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

Two Fixes:

	* Intel VT-d fix for a suspend/resume issue, introduced with the
	  scalability improvements in this cycle.

	* AMD IOMMU fix for systems that have unity mappings defined. There was
	  a race where translation got enabled before the unity mappings were
	  in place. This issue was seen on some HP servers.

----------------------------------------------------------------
Aaron Campbell (1):
      iommu/vt-d: Fix infinite loop in free_all_cpu_cached_iovas

Joerg Roedel (1):
      iommu/amd: Fix unity mapping initialization race

 drivers/iommu/amd_iommu_init.c | 14 ++++++++++++--
 drivers/iommu/intel-iommu.c    |  4 ++--
 2 files changed, 14 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 --]



WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <joro@8bytes.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org
Subject: [git pull] IOMMU Fixes for Linux v4.7-rc6
Date: Fri, 8 Jul 2016 16:30:56 +0200	[thread overview]
Message-ID: <20160708143046.GA1093@8bytes.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1237 bytes --]

Hi Linus,

The following changes since commit a99cde438de0c4c0cecc1d1af1a55a75b10bfdef:

  Linux 4.7-rc6 (2016-07-03 23:01:00 -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-rc6

for you to fetch changes up to 522e5cb76d0663c88f96b6a8301451c8efa37207:

  iommu/amd: Fix unity mapping initialization race (2016-07-06 18:04:55 +0200)

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

Two Fixes:

	* Intel VT-d fix for a suspend/resume issue, introduced with the
	  scalability improvements in this cycle.

	* AMD IOMMU fix for systems that have unity mappings defined. There was
	  a race where translation got enabled before the unity mappings were
	  in place. This issue was seen on some HP servers.

----------------------------------------------------------------
Aaron Campbell (1):
      iommu/vt-d: Fix infinite loop in free_all_cpu_cached_iovas

Joerg Roedel (1):
      iommu/amd: Fix unity mapping initialization race

 drivers/iommu/amd_iommu_init.c | 14 ++++++++++++--
 drivers/iommu/intel-iommu.c    |  4 ++--
 2 files changed, 14 insertions(+), 4 deletions(-)

Please pull.

Thanks,

	Joerg

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

             reply	other threads:[~2016-07-08 14:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-08 14:30 Joerg Roedel [this message]
2016-07-08 14:30 ` [git pull] IOMMU Fixes for Linux v4.7-rc6 Joerg Roedel

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=20160708143046.GA1093@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.