[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <SJ1PR11MB6083FC3839693001C229E78FFCF9A@SJ1PR11MB6083.namprd11.prod.outlook.com>
Date: Wed, 20 Sep 2023 16:09:24 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: Yazen Ghannam <yazen.ghannam@....com>,
Borislav Petkov <bp@...en8.de>
CC: "Smita.KoralahalliChannabasappa@....com"
<Smita.KoralahalliChannabasappa@....com>,
"dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>,
"x86@...nel.org" <x86@...nel.org>,
"linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"patches@...ts.linux.dev" <patches@...ts.linux.dev>
Subject: RE: [PATCH v7 2/3] x86/mce: Add per-bank CMCI storm mitigation
> I was just thinking, could we put all this code in threshold.c? That is
> the place for common thresholding support. And the CMCI storm handling
> seems like it'd be part of that.
Yazen,
I'll take a look at doing that. It might need to drop a handful of "static"
declarations of things in core.c to allow access from another file. But
it should just be a few. This code only hooks into a few spots.
-Tony
P.S. Thanks also for the detailed reviews you posted yesterday. I'm
still digesting those.
Powered by blists - more mailing lists