Linux ATA/IDE development
 help / color / mirror / Atom feed
From: Mario Limonciello <mario.limonciello@amd.com>
To: sashiko-reviews@lists.linux.dev
Cc: cassel@kernel.org, linux-ide@vger.kernel.org, dlemoal@kernel.org,
	linux-pci@vger.kernel.org
Subject: Re: [PATCH 1/2] x86/PCI: Disable enhanced atomics on some AMD PCIe ports
Date: Tue, 8 Sep 2026 12:25:21 -0500	[thread overview]
Message-ID: <391cde44-dab2-49f1-8f57-bd5ba5314ecf@amd.com> (raw)
In-Reply-To: <20260908171427.A111A1F00A3A@smtp.kernel.org>



On 9/8/26 12:14, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Critical] Hardware state loss across suspend/resume causing data corruption
> --
> 
> commit 6c1c185449d3f44e1db8d42c0f5b1f2a64c2eeb8
> Author: Mario Limonciello <mario.limonciello@amd.com>
> 
> x86/PCI: Disable enhanced atomics on some AMD PCIe ports
> 
> This commit disables enhanced atomic operations on PCIe ports for AMD
> NBIO 7.7 and 7.11 based models to prevent data corruption with 64-bit DMA.
> The issue occurs when the 32-bit IOVA space is exhausted on certain BIOSes.
> 
> Closes: https://lore.kernel.org/all/178789300872.392066.15963676631650361573@gmail.com/
> Closes: https://lore.kernel.org/linux-ide/20260406222335.379935-1-artmoty@gmail.com/
> Closes: https://lore.kernel.org/linux-ide/20260621100844.1224301-1-alvinwylim@gmail.com/
> 
>> diff --git a/arch/x86/pci/fixup.c b/arch/x86/pci/fixup.c
>> index b301c6c8df753..0857fd9365ec2 100644
>> --- a/arch/x86/pci/fixup.c
>> +++ b/arch/x86/pci/fixup.c
> 
> [ ... ]
> 
>> +/* Phoenix, Hawk Point (NBIO 7.7) */
>> +DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_AMD, 0x14E8,
>> +			quirk_amd_nbio_7_7_disable_enhanced_atomic);
>> +
>> +/* Strix, Krackan, Strix Halo (NBIO 7.11) */
>> +DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_AMD, 0x1507,
>> +			quirk_amd_nbio_7_11_disable_enhanced_atomic);
>> +DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_AMD, 0x1122,
>> +			quirk_amd_nbio_7_11_disable_enhanced_atomic);
> 
> [Severity: Critical]
> Is this fixup lost across suspend and resume cycles?
> 
> Because the quirk is only registered for the final boot phase using
> DECLARE_PCI_FIXUP_FINAL, the PCI core will not re-apply it during system
> wake (which relies on DECLARE_PCI_FIXUP_RESUME).
> 
> If the system suspends to S3 or s2idle, the NBIO power domain is gated and
> SMN registers lose their state. When the system resumes, the firmware
> re-initializes these SMN registers to their default state (which has
> enhanced atomics enabled).
> 
> Because the kernel does not re-apply the quirk on resume, any subsequent
> 64-bit DMA traffic after waking from sleep could trigger the data
> corruption this code is intended to prevent.
> 
> Should these quirks also be registered with DECLARE_PCI_FIXUP_RESUME?
> 

This looks like valid feedback.  I checked and these registers don't 
surive suspend/resume.  I'll modify it for a v2.

  reply	other threads:[~2026-09-08 17:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-08 17:00 [PATCH 0/2] Fix for storage corruption w/ AMD IOMMU on 64-bit DMA Mario Limonciello
2026-09-08 17:00 ` [PATCH 1/2] x86/PCI: Disable enhanced atomics on some AMD PCIe ports Mario Limonciello
2026-09-08 17:14   ` sashiko-bot
2026-09-08 17:25     ` Mario Limonciello [this message]
2026-09-08 19:18   ` Bjorn Helgaas
2026-09-08 19:19     ` Mario Limonciello
2026-09-08 17:00 ` [PATCH 2/2] Revert "ata: ahci: force 32-bit DMA for JMicron JMB582/JMB585" Mario Limonciello
2026-09-08 17:06   ` sashiko-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=391cde44-dab2-49f1-8f57-bd5ba5314ecf@amd.com \
    --to=mario.limonciello@amd.com \
    --cc=cassel@kernel.org \
    --cc=dlemoal@kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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