[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <SJ1PR11MB6083962F7F6C4C535EE1CB94FCAAA@SJ1PR11MB6083.namprd11.prod.outlook.com>
Date: Mon, 6 Nov 2023 20:42:29 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: Avadhut Naik <avadhut.naik@....com>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>
CC: "rafael@...nel.org" <rafael@...nel.org>,
"lenb@...nel.org" <lenb@...nel.org>,
"james.morse@....com" <james.morse@....com>,
"bp@...en8.de" <bp@...en8.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"yazen.ghannam@....com" <yazen.ghannam@....com>,
"avadnaik@....com" <avadnaik@....com>
Subject: RE: [RESEND v2] ACPI: APEI: Skip initialization of GHES_ASSIST
structures for Machine Check Architecture
> To support GHES_ASSIST on Machine Check Architecture (MCA) error sources,
> a set of GHES structures is provided by the system firmware for each MCA
> error source. Each of these sets consists of a GHES structure for each MCA
> bank on each logical CPU, with all structures of a set sharing a common
> Related Source ID, equal to the Source ID of one of the MCA error source
> structures.[1] On SOCs with large core counts, this typically equates to
> tens of thousands of GHES_ASSIST structures for MCA under
> "/sys/bus/platform/drivers/GHES".
What combination of CONFIG options and BIOS table support results in this?
I don't see much under "/sys/bus/platform/drivers/GHES" on my lab machine
(Dual socket * 36 cores * HT = 144 logical CPUs).
-Tony
Powered by blists - more mailing lists