[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <SJ1PR11MB6083F74E1C45F06860A29A38FC442@SJ1PR11MB6083.namprd11.prod.outlook.com>
Date: Thu, 8 Feb 2024 18:39:05 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: "Naik, Avadhut" <avadnaik@....com>, "x86@...nel.org" <x86@...nel.org>,
"linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>
CC: "bp@...en8.de" <bp@...en8.de>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>, "yazen.ghannam@....com"
<yazen.ghannam@....com>, Avadhut Naik <avadhut.naik@....com>
Subject: RE: [PATCH 1/2] x86/MCE: Extend size of the MCE Records pool
> Will change it to (2 * sizeof(struct mce)) though. Feels more
> accurate. Thanks for the suggestion!
Thanks.
> Do you have any additional concerns/comments on this patchset?
Overall this is an excellent addition. Reserved space to log errors does need to scale
up with the CPU count.
I think part 1 (unconditional increase based on CPU count) is a "must have" enhancement.
With the change to CPU_GEN_MEMSZ #define:
Reviewed-by: Tony Luck <tony.luck@...el.com>
I'm less enthusiastic about part 2 adding a command line option to override the code in
part 1 with a bigger (or smaller?) amount. Can you describe some situation where a user
would need to use this?
-Tony
Powered by blists - more mailing lists