From: Mario Limonciello <mario.limonciello@amd.com>
To: regressions <regressions@lists.linux.dev>, stable@vger.kernel.org
Cc: iommu@lists.linux.dev, "Hegde, Vasant" <Vasant.Hegde@amd.com>,
"Hou, Lizhi" <lizhi.hou@amd.com>
Subject: IOMMU regression in linux-6.18.y
Date: Tue, 20 Jan 2026 20:08:33 -0600 [thread overview]
Message-ID: <870872aa-28e9-412a-bac6-8020bf560e4f@amd.com> (raw)
Hi,
Recently I found out that amdxdna stopped working in linux-6.18.4. This
is because of this commit in linux-6.18.y:
commit c341dee80b5d ("iommu: disable SVA when CONFIG_X86 is set")
That was originally backported from upstream:
commit 72f98ef9a4be ("iommu: disable SVA when CONFIG_X86 is set")
---
SVA support is a requirement for amdxdna.
The series that this commit came from was part of a larger 8 patch
series, but this was the only commit that was CC'ed to stable.
As a result this is not broken in 6.19-rc, but it is broken in
linux-6.18.y (and presumably any older stable kernels still around that
picked it up).
So there are two options I see:
1) Revert c341dee80b5d in linux-6.18.y (and any other stable kernel that
picked it up but has amdxdna)
2) Bring the entire 8 patch series to linux-6.18.y.
This is the entire series (I didn't look up the hashes from mainline,
but they should have all landed):
https://lore.kernel.org/linux-iommu/20251022082635.2462433-1-baolu.lu@linux.intel.com/
What should we do?
next reply other threads:[~2026-01-21 2:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 2:08 Mario Limonciello [this message]
2026-01-21 5:26 ` IOMMU regression in linux-6.18.y Mario Limonciello
2026-01-21 7:14 ` Baolu Lu
2026-01-21 7:26 ` Greg KH
2026-01-21 7:32 ` Baolu Lu
2026-01-21 14:55 ` Greg KH
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=870872aa-28e9-412a-bac6-8020bf560e4f@amd.com \
--to=mario.limonciello@amd.com \
--cc=Vasant.Hegde@amd.com \
--cc=iommu@lists.linux.dev \
--cc=lizhi.hou@amd.com \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.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