From: Yazen Ghannam <yazen.ghannam@amd.com>
To: "Luck, Tony" <tony.luck@intel.com>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>
Cc: yazen.ghannam@amd.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>
Subject: Re: [PATCH 1/2] x86/mce: Disable preemption for CPER decoding
Date: Thu, 22 Jun 2023 12:24:15 -0400 [thread overview]
Message-ID: <f03b6c61-1669-c03e-310c-cc1364cf30a8@amd.com> (raw)
In-Reply-To: <SJ1PR11MB6083664BCFC8047A5FE8F6A9FC22A@SJ1PR11MB6083.namprd11.prod.outlook.com>
On 6/22/2023 11:35 AM, Luck, Tony wrote:
>> All the above is done when the BERT is processed during late init. This
>> can be scheduled on any CPU, and it may be preemptible.
>
>> 2) mce_setup() will pull info from the executing CPU, so some info in
>> struct mce may be incorrect for the CPU with the error. For example,
>> in a dual-socket system, an error logged in socket 1 CPU but
>> processed by a socket 0 CPU will save the PPIN of the socket 0 CPU.
>
>> Fix the first issue by locally disabling preemption before calling
>> mce_setup().
>
> It doesn't really fix the issue, it just makes the warnings go away.
>
> The BERT record was created because some error crashed the
> system. It's being parsed by a CPU that likely had nothing
> to do with the actual error that occurred in the previous incarnation
> of the OS.
>
Yes, these are true statements.
> If there is a CPER record in the BERT data that includes CPU
> information, that would be the right thing to use. Alternatively
> is there some invalid CPU value that could be loaded into the
> "struct mce"?
>
This is the reason we search for the logical CPU number using the Local
APIC ID provided in the CPER. And fill in relevant data using that CPU
number.
Thanks,
Yazen
next prev parent reply other threads:[~2023-06-22 16:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 13:18 [PATCH 0/2] SMCA CPER Fixes Yazen Ghannam
2023-06-22 13:18 ` [PATCH 1/2] x86/mce: Disable preemption for CPER decoding Yazen Ghannam
2023-06-22 15:35 ` Luck, Tony
2023-06-22 16:24 ` Yazen Ghannam [this message]
2023-06-22 17:05 ` Luck, Tony
2023-06-22 19:23 ` Yazen Ghannam
2023-06-22 19:42 ` Luck, Tony
2023-06-23 13:51 ` Yazen Ghannam
2023-06-23 15:44 ` Luck, Tony
2023-06-23 16:01 ` Borislav Petkov
2023-06-23 16:14 ` Yazen Ghannam
2023-06-23 16:42 ` Borislav Petkov
2023-06-26 14:47 ` Yazen Ghannam
2023-06-22 13:18 ` [PATCH 2/2] x86/mce: Set correct PPIN " Yazen Ghannam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f03b6c61-1669-c03e-310c-cc1364cf30a8@amd.com \
--to=yazen.ghannam@amd.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox