From: Joerg Roedel <joro@8bytes.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Will Deacon <will@kernel.org>,
linux-kernel@vger.kernel.org, iommu@lists.linux.dev
Subject: [git pull] IOMMU Fixes for Linux v7.3-rc2
Date: Sat, 12 Sep 2026 10:32:55 +0200 [thread overview]
Message-ID: <aqUOFhjG7gjWfpAf@8bytes.org> (raw)
Hi Linus,
The following changes since commit df2908090cda368b01ff43709f51890076c56157:
Linux 7.3-rc2 (2026-09-06 15:07:20 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/iommu/linux.git tags/iommu-fixes-v7.3-rc2
for you to fetch changes up to b63c3c26726576e2a87baeee80bc202a5a43c9e5:
iommu/amd: Remove unused macro (2026-09-11 17:27:22 +0200)
----------------------------------------------------------------
IOMMU fixes for Linux v7.3-rc3:
- RISC-V IOMMU:
- Serialize command queue publication to prevent concurrent producers
from exposing incomplete or out-of-order commands to hardware.
- Wait for queue space outside the command queue lock.
- Avoid waiting for IOFENCE completion when command enqueue failed.
- AMD IOMMU:
- Prevent GA log buffers from being reallocated and leaked during
resume, where allocation also occurs in an unsuitable syscore
callback context.
- Fix a regression on older systems whose firmware advertises
incorrect IOMMU features.
- Preserve allocation errors when assigning host domain IDs to nested
domains.
- s390 IOMMU:
- Prevent a NULL dereference when translating an unmapped IOVA with
five-level ZPCI translation tables.
- Miscellaneous:
- Remove a stale MAINTAINERS entry and clean up unused or redundant
AMD IOMMU declarations, macros, and checks.
----------------------------------------------------------------
Daasaradhi Mannava (1):
MAINTAINERS: Drop the nonexistent vsi-iommu.h file entry
Fangyu Yu (3):
iommu/riscv: Add command queue lock
iommu/riscv: Serialize command queue publishing
iommu/riscv: Avoid waiting on failed command enqueue
Hemanth Selam (1):
iommu/amd: Fix ineffective error check in nested domain allocation
Karl Mehltretter (1):
iommu/amd: Do not reallocate GA log buffers on resume
Niklas Schnelle (1):
iommu/s390: Fix NULL dereference in iova_to_phys() with ZPCI_TABLE_TYPE_RFX
Vasant Hegde (5):
iommu/amd: Fix premature break in init_iommu_one() again
iommu/amd: Make iommu_sva_set_dev_pasid as static
iommu/amd: Remove redundant check in irq_remapping_select()
iommu/amd: Remove redundant checks from interrupt handler path
iommu/amd: Remove unused macro
MAINTAINERS | 1 -
drivers/iommu/amd/amd_iommu.h | 3 -
drivers/iommu/amd/amd_iommu_types.h | 16 -----
drivers/iommu/amd/init.c | 18 ++++--
drivers/iommu/amd/iommu.c | 6 --
drivers/iommu/amd/nested.c | 7 ++-
drivers/iommu/amd/pasid.c | 6 +-
drivers/iommu/amd/ppr.c | 3 -
drivers/iommu/riscv/iommu.c | 117 +++++++++++++++++++++---------------
drivers/iommu/riscv/iommu.h | 2 +
drivers/iommu/s390-iommu.c | 2 +
11 files changed, 93 insertions(+), 88 deletions(-)
Please pull.
Thanks,
Joerg
next reply other threads:[~2026-09-12 8:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-12 8:32 Joerg Roedel [this message]
2026-09-12 15:16 ` 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=aqUOFhjG7gjWfpAf@8bytes.org \
--to=joro@8bytes.org \
--cc=iommu@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=will@kernel.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
all inboxes | Powered by JetHome®