Linux ATA/IDE development
 help / color / mirror / Atom feed
From: Niklas Cassel <cassel@kernel.org>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: Roland Waltersson <roland.waltersson@netinsight.net>,
	"artmoty@gmail.com" <artmoty@gmail.com>,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
	David Laight <david.laight.linux@gmail.com>,
	Mikael Etienne <mikael1022bzh@gmail.com>,
	Alvin Lim <alvinwylim@gmail.com>,
	Lennert Buytenhek <kernel@wantstofly.org>
Subject: Re: [PATCH] ahci: force 32-bit DMA for JMicron JMB582/JMB585
Date: Fri, 4 Sep 2026 14:50:15 +0200	[thread overview]
Message-ID: <apq-h4SKix_zn3ni@ryzen> (raw)
In-Reply-To: <07efa8b1-c5ef-4a61-8b0c-45f68d02d9f5@amd.com>

On Fri, Sep 04, 2026 at 07:38:06AM -0500, Mario Limonciello wrote:
> On 9/4/26 06:14, Niklas Cassel wrote:
> > 
> > 2) A fix for the AMD IOMMU driver to be merged, and backported to stable,
> > such that us writing a fix that drops the 32-bit only DMA quirk for JMicron
> > JMB582/585, which when backported to stable, will not cause users with an
> > AMD IOMMU to silently get their filesystem corrupted.
> > 
> > 
> 
> Right now what I'm thinking of doing is a quirk in arch/x86/pci/fixup.c to
> set the registers that could influence this issue.
> 
> An alternative may be some quirks to the AMD IOMMU driver to avoid using the
> upper 5 bits for the IOVA allocations (making it 59 bit).

No stress with regards to JMB582/585. We will keep the quirk as long as it
is needed to avoid the AMD IOMMU issue, but please CC me if you send out a
fix.

It is probably worse for those like Mikael Etienne, who is using an AMD 600
Series Chipset SATA Controller [1022:43f6], since for those SATA controllers,
we do not have a 32-bit only quirk that hides/workarounds the problem.


Kind regards,
Niklas

  reply	other threads:[~2026-09-04 12:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-03 13:35 [PATCH] ahci: force 32-bit DMA for JMicron JMB582/JMB585 Roland Waltersson
2026-09-03 21:40 ` Niklas Cassel
2026-09-03 22:36   ` Mario Limonciello
2026-09-04  5:20     ` Roland Waltersson
2026-09-04 11:14       ` Niklas Cassel
2026-09-04 12:38         ` Mario Limonciello
2026-09-04 12:50           ` Niklas Cassel [this message]
2026-09-04 16:55             ` Mikael Etienne
2026-09-05 11:38               ` Alvin Lim
2026-09-05 12:26                 ` Mario Limonciello
  -- strict thread matches above, loose matches on Subject: below --
2026-04-03  5:04 Arthur Husband
2026-04-03  7:02 ` Damien Le Moal
2026-04-03  8:12 ` Niklas Cassel
2026-04-03  8:19 ` Niklas Cassel
2026-04-03  5:02 Arthur Husband

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=apq-h4SKix_zn3ni@ryzen \
    --to=cassel@kernel.org \
    --cc=alvinwylim@gmail.com \
    --cc=artmoty@gmail.com \
    --cc=david.laight.linux@gmail.com \
    --cc=kernel@wantstofly.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=mikael1022bzh@gmail.com \
    --cc=roland.waltersson@netinsight.net \
    /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