[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240212201840.GOZcp9IFKkmsRT0Sj9@fat_crate.local>
Date: Mon, 12 Feb 2024 21:18:40 +0100
From: Borislav Petkov <bp@...en8.de>
To: "Naik, Avadhut" <avadnaik@....com>
Cc: "Luck, Tony" <tony.luck@...el.com>,
Yazen Ghannam <yazen.ghannam@....com>,
"Mehta, Sohil" <sohil.mehta@...el.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>,
Avadhut Naik <avadhut.naik@....com>
Subject: Re: [PATCH 2/2] x86/MCE: Add command line option to extend MCE
Records pool
On Mon, Feb 12, 2024 at 01:40:21PM -0600, Naik, Avadhut wrote:
> The spinlock is mostly held to prevent other primitives
> from modifying chunks within the genpool.
>
> In #MC context however, we are not modifying the existing
> chunks, per se.
What if we decide to do
mce[i]count++;
in #MC context?
That's modifying the existing chunks.
TBH, I'm not sure what that spinlock is for. See my reply to that same
subthread.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists