From: Mario Limonciello <mario.limonciello@amd.com>
To: Yazen Ghannam <yazen.ghannam@amd.com>
Cc: Borislav Petkov <bp@alien8.de>, Tony Luck <tony.luck@intel.com>,
superm1@kernel.org, linux-edac@vger.kernel.org,
Shrirang Deskhmukh <Shrirang.Deskhmukh@amd.com>
Subject: Re: [PATCH] RAS/AMD/ATL: Decrease message about unknown DF revision to debug
Date: Thu, 19 Mar 2026 22:30:02 -0500 [thread overview]
Message-ID: <6e752d2b-c52b-4077-85bd-b54c7da4868e@amd.com> (raw)
In-Reply-To: <20260319143634.GB1639900@yaz-khff2.amd.com>
On 3/19/2026 9:36 AM, Yazen Ghannam wrote:
> On Wed, Mar 18, 2026 at 10:43:04AM -0500, Mario Limonciello wrote:
>
> [...]
>
>>> diff --git a/drivers/ras/amd/atl/core.c b/drivers/ras/amd/atl/core.c
>>> index 0f7cd6dab0b0..d77dacdd4f56 100644
>>> --- a/drivers/ras/amd/atl/core.c
>>> +++ b/drivers/ras/amd/atl/core.c
>>> @@ -190,7 +190,6 @@ static const struct x86_cpu_id amd_atl_cpuids[] = {
>>> X86_MATCH_FEATURE(X86_FEATURE_ZEN, NULL),
>>> { }
>>> };
>>> -MODULE_DEVICE_TABLE(x86cpu, amd_atl_cpuids);
>>
>> Pretty sure this means you can drop amd_atl_cpuids as well.
>
> Yeah, maybe.
>
> The request_module() in EDAC is unconditional. We use the same EDAC
> module for multiple generations of CPUs.
>
> The amd_atl_cpuids check will keep the amd_atl module off the legacy
> systems.
>
> We could redo the flow. But there needs to be a feature check somewhere.
> The proposed patch is the smallest diff I thought of at the time.
>
> Thanks,
> Yazen
Well to be fair there was CPU no check before - the module device table
just controlled automatic loading.
But yeah I think a simple cpu feature check during probe along with the
suggested change would solve this.
prev parent reply other threads:[~2026-03-20 3:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 15:45 [PATCH] RAS/AMD/ATL: Decrease message about unknown DF revision to debug Mario Limonciello
2026-03-06 14:50 ` Borislav Petkov
2026-03-06 15:03 ` Mario Limonciello
2026-03-06 15:32 ` Borislav Petkov
2026-03-06 15:40 ` Mario Limonciello
2026-03-06 15:49 ` Borislav Petkov
2026-03-07 14:49 ` Yazen Ghannam
2026-03-07 15:12 ` Borislav Petkov
2026-03-10 12:54 ` Yazen Ghannam
2026-03-10 14:58 ` Mario Limonciello
2026-03-10 16:52 ` Yazen Ghannam
2026-03-10 17:47 ` Mario Limonciello
2026-03-11 13:38 ` Yazen Ghannam
2026-03-11 14:28 ` Mario Limonciello
2026-03-18 15:43 ` Mario Limonciello
2026-03-19 14:36 ` Yazen Ghannam
2026-03-20 3:30 ` Mario Limonciello [this message]
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=6e752d2b-c52b-4077-85bd-b54c7da4868e@amd.com \
--to=mario.limonciello@amd.com \
--cc=Shrirang.Deskhmukh@amd.com \
--cc=bp@alien8.de \
--cc=linux-edac@vger.kernel.org \
--cc=superm1@kernel.org \
--cc=tony.luck@intel.com \
--cc=yazen.ghannam@amd.com \
/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