Received-SPF: pass (google.com: domain of linux-kernel+bounces-65803-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) client-ip=147.75.80.249;
Date: Wed, 14 Feb 2024 19:29:53 +0100
From: Borislav Petkov <bp@alien8.de>
To: Yazen Ghannam <yazen.ghannam@amd.com>
Cc: tony.luck@intel.com, linux-edac@vger.kernel.org,
	linux-kernel@vger.kernel.org, avadhut.naik@amd.com,
	john.allen@amd.com, muralidhara.mk@amd.com,
	naveenkrishna.chatradhi@amd.com, sathyapriya.k@amd.com
Subject: Re: [PATCH 2/2] RAS: Introduce the FRU Memory Poison Manager
Message-ID: <20240214182953.GMZc0GofSSQxd3T5-N@fat_crate.local>
References: <20240214033516.1344948-1-yazen.ghannam@amd.com>
 <20240214033516.1344948-3-yazen.ghannam@amd.com>
 <20240214103446.GDZcyXRkyf1bFzMh7L@fat_crate.local>
 <3bc7bef5-9cfc-400a-a1ba-99ebf5d94952@amd.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <3bc7bef5-9cfc-400a-a1ba-99ebf5d94952@amd.com>

On Wed, Feb 14, 2024 at 09:46:46AM -0500, Yazen Ghannam wrote:
> > This is a generic thing and thus can't use an x86-ism struct mce,
> > remember?
> > 
> 
> Yep, that's one of the assumptions/limitations I highlighted.

Right, since the notifier callback fru_mem_poison_nb is on the x86 MCE
chain and since we're making this thing depend on AMD_ATL which depends
on X86_64 currently, it is ok to have struct mce in there.

Once something else outside of x86 wants to use it, it'll have to be
decoupled and use atl_err.

Later...

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette