From: Mikael Etienne <mikael1022bzh@gmail.com>
To: cassel@kernel.org, mario.limonciello@amd.com
Cc: roland.waltersson@netinsight.net, artmoty@gmail.com,
linux-ide@vger.kernel.org, david.laight.linux@gmail.com,
alvinwylim@gmail.com, kernel@wantstofly.org
Subject: Re: [PATCH] ahci: force 32-bit DMA for JMicron JMB582/JMB585
Date: Fri, 04 Sep 2026 23:55:38 +0700 [thread overview]
Message-ID: <178854093896.541085.18395405788748617410@gmail.com> (raw)
In-Reply-To: <apq-h4SKix_zn3ni@ryzen>
Hi Niklas,
You asked whether there might be different versions of the AMD IOMMU. Here is my
full identification, so this can be compared rather than guessed:
CPU : AMD Ryzen 7 8700G w/ Radeon 780M (Phoenix), family 25, model 117,
stepping 2
Controller : AMD 600 Series Chipset SATA Controller [1022:43f6]
Table : ACPI IVRS v02 (AMD / AmdTable)
IVHD : AMD-Vi: Using global IVHD EFR:0x246577efa2254afa, EFR2:0x0
Kernel : 7.1.x, Fedora 44
The EFR field is probably the most direct discriminant. If Arthur, Alvin and
Lennert posted the same line, the "different IOMMU versions" hypothesis could be
tested immediately, with no extra hardware:
journalctl -k -b | grep -E "IVHD EFR|IVRS"
That would be particularly worth it for Alvin, since iommu=pt is insufficient
for him while it is completely clean for me -- that is the only divergence
between our reports.
I cannot be your tester for point 1, unfortunately: I have neither a JMB582/585
nor an Intel or ARM IOMMU. The reproducer you quoted is current; one
clarification, fio verifies its own CRC32C, so the result does not depend on the
underlying filesystem.
On your point 2: I am working with Mario on the AMD IOMMU side. I have committed
to testing on my 600-series and reporting the outcome in the regression thread,
positive or negative. I cannot give a date -- the machine is under maintenance
work -- but I will report either way.
Kind regards,
Mikael Etienne
next prev parent reply other threads:[~2026-09-04 16:55 UTC|newest]
Thread overview: 13+ 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
2026-09-04 16:55 ` Mikael Etienne [this message]
-- 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=178854093896.541085.18395405788748617410@gmail.com \
--to=mikael1022bzh@gmail.com \
--cc=alvinwylim@gmail.com \
--cc=artmoty@gmail.com \
--cc=cassel@kernel.org \
--cc=david.laight.linux@gmail.com \
--cc=kernel@wantstofly.org \
--cc=linux-ide@vger.kernel.org \
--cc=mario.limonciello@amd.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