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.6-rc5
Date: Sun, 15 Mar 2020 10:16:10 +0100 [thread overview]
Message-ID: <20200315091602.GA18173@8bytes.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2721 bytes --]
Hi Linus,
The following changes since commit 98d54f81e36ba3bf92172791eba5ca5bd813989b:
Linux 5.6-rc4 (2020-03-01 16:38:46 -0600)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git tags/iommu-fixes-v5.6-rc5
for you to fetch changes up to 1da8347d8505c137fb07ff06bbcd3f2bf37409bc:
iommu/vt-d: Populate debugfs if IOMMUs are detected (2020-03-14 20:02:43 +0100)
----------------------------------------------------------------
IOMMU Fixes for Linux v5.6-rc5
Including:
- Mostly Intel VT-d fixes:
- RCU list handling fixes
- Replace WARN_TAINT with pr_warn + add_taint for reporting
firmware issues
- DebugFS fixes
- Fix for hugepage handling in iova_to_phys implementation
- Fix for handling VMD devices, which have a domain number
which doesn't fit into 16 bits
- Warning message fix
- MSI allocation fix for iommu-dma code
- Sign-extension fix for io page-table code
- Fix for AMD-Vi to properly update the is-running bit when
AVIC is used
----------------------------------------------------------------
Amol Grover (1):
iommu/vt-d: Fix RCU list debugging warnings
Daniel Drake (1):
iommu/vt-d: Ignore devices with out-of-spec domain number
Hans de Goede (3):
iommu/vt-d: dmar: replace WARN_TAINT with pr_warn + add_taint
iommu/vt-d: dmar_parse_one_rmrr: replace WARN_TAINT with pr_warn + add_taint
iommu/vt-d: quirk_ioat_snb_local_iommu: replace WARN_TAINT with pr_warn + add_taint
Marc Zyngier (1):
iommu/dma: Fix MSI reservation allocation
Megha Dey (2):
iommu/vt-d: Fix debugfs register reads
iommu/vt-d: Populate debugfs if IOMMUs are detected
Qian Cai (2):
iommu/vt-d: Fix RCU-list bugs in intel_iommu_init()
iommu/vt-d: Silence RCU-list debugging warnings
Robin Murphy (1):
iommu/io-pgtable-arm: Fix IOVA validation for 32-bit
Suravee Suthikulpanit (1):
iommu/amd: Fix IOMMU AVIC not properly update the is_run bit in IRTE
Yonghyun Hwang (1):
iommu/vt-d: Fix a bug in intel_iommu_iova_to_phys() for huge page
Zhenzhong Duan (1):
iommu/vt-d: Fix the wrong printing in RHSA parsing
drivers/iommu/amd_iommu.c | 4 +--
drivers/iommu/dma-iommu.c | 16 ++++++------
drivers/iommu/dmar.c | 24 ++++++++++++-----
drivers/iommu/intel-iommu-debugfs.c | 51 +++++++++++++++++++++++++------------
drivers/iommu/intel-iommu.c | 28 +++++++++++++-------
drivers/iommu/io-pgtable-arm.c | 4 +--
include/linux/dmar.h | 14 ++++++----
include/linux/intel-iommu.h | 2 ++
8 files changed, 94 insertions(+), 49 deletions(-)
Please pull.
Thanks,
Joerg
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2020-03-15 9:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-15 9:16 Joerg Roedel [this message]
2020-03-15 20:25 ` [git pull] IOMMU Fixes for Linux v5.6-rc5 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=20200315091602.GA18173@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;
as well as URLs for NNTP newsgroup(s).