From: Yazen Ghannam <yazen.ghannam@amd.com>
To: Borislav Petkov <bp@alien8.de>
Cc: linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org,
tony.luck@intel.com, x86@kernel.org
Subject: Re: [PATCH] x86/mce/amd, EDAC/mce_amd: Add new SMCA bank types
Date: Wed, 4 Mar 2026 13:02:20 -0500 [thread overview]
Message-ID: <20260304180220.GA980523@yaz-khff2.amd.com> (raw)
In-Reply-To: <20260304163953.GAaahgWQIZ5QuxLDP5@fat_crate.local>
On Wed, Mar 04, 2026 at 05:39:53PM +0100, Borislav Petkov wrote:
> On Wed, Mar 04, 2026 at 10:04:02AM -0500, Yazen Ghannam wrote:
> > We can re-sort them. Still want to have them alphabetically?
>
> I'm not sure how yet - all I'm trying to say is that random order is kinda
> suboptimal when having to look at the code.
>
> Alphabetically probably sounds ok because you have 0xb0 ones, for example,
> which belong to different banks which makes me think that the hwid in
> HWID_MCATYPE(hwid, mcatype) is perhaps arbitrary and not very important.
The HWID and McaType are defined in the hardware. The name/enum is
arbitrary, and we use those for convenience.
Some of the HWID represent a group of IP, e.g. 0xb0 is (so far) used for
Core banks, 0x2e for Fabric, etc.
So far we haven't needed to use HWID on its own. Though I had a patch to
check for a "memory controller" type by HWID=0x96.
https://lore.kernel.org/all/20231118193248.1296798-6-yazen.ghannam@amd.com/
Though maybe you mean "sorting based on HWID/McaType" is not important?
I agree.
>
> And perhaps we can work better with alphabetically sorted IP names...
>
> Rite?
>
> > I can re-sort in a pre-patch before adding the new ones.
>
> Yeah, makes sense.
>
Okay, I'll work on it.
Thanks,
Yazen
next prev parent reply other threads:[~2026-03-04 18:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 17:21 [PATCH] x86/mce/amd, EDAC/mce_amd: Add new SMCA bank types Yazen Ghannam
2026-02-28 15:04 ` Borislav Petkov
2026-03-02 14:22 ` Yazen Ghannam
2026-03-03 15:38 ` Borislav Petkov
2026-03-04 15:04 ` Yazen Ghannam
2026-03-04 16:39 ` Borislav Petkov
2026-03-04 18:02 ` Yazen Ghannam [this message]
2026-03-04 20:24 ` Borislav Petkov
-- strict thread matches above, loose matches on Subject: below --
2021-05-01 16:16 [PATCH] x86/MCE/AMD, " Muralidhara M K
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=20260304180220.GA980523@yaz-khff2.amd.com \
--to=yazen.ghannam@amd.com \
--cc=bp@alien8.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
--cc=x86@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