From: Yazen Ghannam <yazen.ghannam@amd.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Naveen Krishna Chatradhi <naveenkrishna.chatradhi@amd.com>,
Muralidhara M K <muralidhara.mk@amd.com>,
linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] RAS/AMD/{ATL,FMPM}: Get masked address
Date: Tue, 8 Apr 2025 16:10:55 -0400 [thread overview]
Message-ID: <20250408201055.GA2700280@yaz-khff2.amd.com> (raw)
In-Reply-To: <20250408173333.GEZ_Vd7V0hqJfBXFRu@fat_crate.local>
On Tue, Apr 08, 2025 at 07:33:33PM +0200, Borislav Petkov wrote:
> On Tue, Apr 08, 2025 at 11:52:42AM -0400, Yazen Ghannam wrote:
> > At the moment, FMPM only loads on MI300A. We can just have a local
> > function to mask the addresses. I was thinking we can have function
> > pointers to make things generic. But maybe we keep it simple until
> > really necessary by just using the MI300 version by default.
>
> Now you're talking! :-P
>
> > Please see patch below.
>
> ... which I simplified even more.
>
> I'm thinking whoever is going to test fmpm on something else besides MI300A,
> they will have to extend this address masking thing and then we can cross that
> bridge when we get to it.
>
> So this is keeping it simple for now.
>
> Ack?
Yes, looks good to me.
Thanks!
-Yazen
next prev parent reply other threads:[~2025-04-08 20:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 20:48 [PATCH 0/2] MI300A ATL and FMPM fixes Yazen Ghannam
2025-04-01 20:49 ` [PATCH 1/2] RAS/AMD/ATL: Include row[13] bit in row retirement Yazen Ghannam
2025-04-01 20:49 ` [PATCH 2/2] RAS/AMD/{ATL,FMPM}: Get masked address Yazen Ghannam
2025-04-07 13:24 ` Borislav Petkov
2025-04-07 15:16 ` Yazen Ghannam
2025-04-08 10:14 ` Borislav Petkov
2025-04-08 15:52 ` Yazen Ghannam
2025-04-08 17:33 ` Borislav Petkov
2025-04-08 20:10 ` Yazen Ghannam [this message]
2025-04-10 9:51 ` Borislav Petkov
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=20250408201055.GA2700280@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=muralidhara.mk@amd.com \
--cc=naveenkrishna.chatradhi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.