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.9-rc3
Date: Sun, 6 Sep 2020 17:01:20 +0200 [thread overview]
Message-ID: <20200906150115.GA29365@8bytes.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2211 bytes --]
Hi Linus,
The following changes since commit f75aef392f869018f78cfedf3c320a6b3fcfda6b:
Linux 5.9-rc3 (2020-08-30 16:01:54 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git tags/iommu-fixes-v5.9-rc3
for you to fetch changes up to 29aaebbca4abc4cceb38738483051abefafb6950:
iommu/vt-d: Handle 36bit addressing for x86-32 (2020-09-04 12:14:28 +0200)
----------------------------------------------------------------
IOMMU Fixes for Linux v5.9-rc3
Including:
- Three Intel VT-d fixes to fix address handling on 32bit, fix a
NULL pointer dereference bug and serialize a hardware register
access as required by the VT-d spec.
- Two patches for AMD IOMMU to force AMD GPUs into translation mode
when memory encryption is active and disallow using IOMMUv2
functionality. This makes the AMDGPU driver working when
memory encryption is active.
- Two more fixes for AMD IOMMU to fix updating the Interrupt
Remapping Table Entries.
- MAINTAINERS file update for the Qualcom IOMMU driver.
----------------------------------------------------------------
Chris Wilson (1):
iommu/vt-d: Handle 36bit addressing for x86-32
Joerg Roedel (2):
iommu/amd: Do not force direct mapping when SME is active
iommu/amd: Do not use IOMMUv2 functionality when SME is active
Lu Baolu (2):
iommu/vt-d: Serialize IOMMU GCMD register modifications
iommu/vt-d: Fix NULL pointer dereference in dev_iommu_priv_set()
Lukas Bulwahn (1):
MAINTAINERS: Update QUALCOMM IOMMU after Arm SMMU drivers move
Suravee Suthikulpanit (2):
iommu/amd: Restore IRTE.RemapEn bit after programming IRTE
iommu/amd: Use cmpxchg_double() when updating 128-bit IRTE
MAINTAINERS | 2 +-
drivers/iommu/amd/Kconfig | 2 +-
drivers/iommu/amd/init.c | 21 ++++++-
drivers/iommu/amd/iommu.c | 26 ++++++--
drivers/iommu/amd/iommu_v2.c | 7 +++
drivers/iommu/intel/iommu.c | 114 ++++++++++++++++++++----------------
drivers/iommu/intel/irq_remapping.c | 10 +++-
7 files changed, 119 insertions(+), 63 deletions(-)
Please pull.
Thanks,
Joerg
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2020-09-06 15:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-06 15:01 Joerg Roedel [this message]
2020-09-06 19:14 ` [git pull] IOMMU Fixes for Linux v5.9-rc3 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=20200906150115.GA29365@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