[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4ba9e6e5-323b-4eb2-b0cd-d10a2f432fde@amd.com>
Date: Mon, 12 Feb 2024 14:51:48 -0600
From: "Naik, Avadhut" <avadnaik@....com>
To: Borislav Petkov <bp@...en8.de>
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: [PATCH 2/2] x86/MCE: Add command line option to extend MCE Records
pool
Hi,
On 2/12/2024 14:18, Borislav Petkov wrote:
> 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.
>
Yes, noticed your reply. Clears most of my confusion.
--
Thanks,
Avadhut Naik
Powered by blists - more mailing lists