[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 8 Aug 2022 21:36:13 +0000
From: "Kani, Toshi" <toshi.kani@....com>
To: Borislav Petkov <bp@...en8.de>
CC: "Rafael J. Wysocki" <rafael@...nel.org>,
Jia He <justin.he@....com>, "Len Brown" <lenb@...nel.org>,
James Morse <james.morse@....com>,
Tony Luck <tony.luck@...el.com>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
"Robert Richter" <rric@...nel.org>,
Shuai Xue <xueshuai@...ux.alibaba.com>,
"Jarkko Sakkinen" <jarkko@...nel.org>,
ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"open list:EDAC-CORE" <linux-edac@...r.kernel.org>
Subject: RE: [PATCH] ACPI: APEI: move edac_init ahead of ghes platform drv
register
On Monday, August 8, 2022 3:21 PM, Borislav Petkov wrote:
> On Mon, Aug 08, 2022 at 09:11:52PM +0000, Kani, Toshi wrote:
> > Whichever loaded first wins.
>
> That I know.
>
> The question is, which one *should* win each time.
>
> IOW, on which platforms should ghes_edac load and on which the chipset-
> one?
Platforms with ACPI GHES support should use ghes_edac. This is the case
on Arm. The x86 side has additional platform ID check to protect from legacy
buggy GHES FW existed before ghes_edac enablement.
Toshi
Powered by blists - more mailing lists