Linux IOMMU Development
 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.10-rc2
Date: Fri, 6 Jan 2017 16:02:15 +0100	[thread overview]
Message-ID: <20170106150209.GA29909@8bytes.org> (raw)


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

Hi Linus,

The following changes since commit 0c744ea4f77d72b3dcebb7a8f2684633ec79be88:

  Linux 4.10-rc2 (2017-01-01 14:31:53 -0800)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git tags/iommu-fixes-v4.10-rc2

for you to fetch changes up to 432abf68a79332282329286d190e21fe3ac02a31:

  iommu/amd: Fix the left value check of cmd buffer (2017-01-04 15:22:22 +0100)

----------------------------------------------------------------
IOMMU Fixes for Linux v4.10-rc2

Three fixes queued up:

	* Fix an issue with command buffer overflow handling in the AMD
	  IOMMU driver

	* Add an additional context entry flush to the Intel VT-d driver
	  to make sure any old context entry from kdump copying is
	  flushed out of the cache

	* Correct the encoding of the PASID table size in the Intel VT-d
	  driver

----------------------------------------------------------------
Huang Rui (1):
      iommu/amd: Fix the left value check of cmd buffer

Jacob Pan (1):
      iommu/vt-d: Fix pasid table size encoding

Xunlei Pang (1):
      iommu/vt-d: Flush old iommu caches for kdump when the device gets context mapped

 drivers/iommu/amd_iommu.c   |  2 +-
 drivers/iommu/intel-iommu.c | 42 +++++++++++++++++++++++++++++++++++++++++-
 2 files changed, 42 insertions(+), 2 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-01-06 15: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=20170106150209.GA29909@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