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 v5.1-rc1
Date: Fri, 22 Mar 2019 12:22:29 +0100 [thread overview]
Message-ID: <20190322112224.GA22496@8bytes.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1392 bytes --]
Hi Linus,
The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:
Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git tags/iommu-fixes-v5.1-rc2
for you to fetch changes up to 84c11e4df5aa4955acaa441f0cf1cb2e50daf64b:
iommu/vt-d: Save the right domain ID used by hardware (2019-03-22 12:02:27 +0100)
----------------------------------------------------------------
IOMMU Fixes for Linux v5.1-rc2
Including:
- AMD IOMMU fix for sg-mapping with sg->offset > PAGE_SIZE
- Fix for IOVA code to trigger the slow-path less often
- Two fixes for Intel VT-d to avoid writing to read-onl registers and
to flush the right domain id for the default domains in scalable
mode
----------------------------------------------------------------
Lu Baolu (2):
iommu/vt-d: Check capability before disabling protected memory
iommu/vt-d: Save the right domain ID used by hardware
Robert Richter (1):
iommu/iova: Fix tracking of recently failed iova address
Stanislaw Gruszka (1):
iommu/amd: fix sg->dma_address for sg->offset bigger than PAGE_SIZE
drivers/iommu/amd_iommu.c | 7 ++++++-
drivers/iommu/intel-iommu.c | 5 ++++-
drivers/iommu/iova.c | 5 +++--
3 files changed, 13 insertions(+), 4 deletions(-)
Please pull.
Thanks,
Joerg
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2019-03-22 11:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-22 11:22 Joerg Roedel [this message]
2019-03-22 21:20 ` [git pull] IOMMU Fixes for Linux v5.1-rc1 pr-tracker-bot
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=20190322112224.GA22496@8bytes.org \
--to=joro@8bytes.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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