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: Fri, 23 Jun 2023 09:51:47 -0400 [thread overview]
Message-ID: <e6b1af5a-774a-c3ef-223e-4595b7ec532a@amd.com> (raw)
In-Reply-To: <SJ1PR11MB60831A6E82329E1C53257F3EFC22A@SJ1PR11MB6083.namprd11.prod.outlook.com>
On 6/22/2023 3:42 PM, Luck, Tony wrote:
>> 2) Split mce_setup() into global and per_cpu parts. The memset(), cpuid,
>> etc. would be global, and the cpu_data()* and rdmsr() would be per_cpu.
>
> That sounds good. So global is:
>
> memset(m, 0, sizeof(struct mce));
> /* need the internal __ version to avoid deadlocks */
> m->time = __ktime_get_real_seconds();
> m->cpuvendor = boot_cpu_data.x86_vendor;
> m->mcgcap = __rdmsr(MSR_IA32_MCG_CAP);
MCG_CAP would be per_cpu, because the bank count can vary. But I don't
think this matters in practice. So leaving it global is okay, I think.
> m->microcode = boot_cpu_data.microcode;
> m->cpuid = cpuid_eax(1);
>
> Though that last one is perhaps per-cpu if you want to allow for mixed-stepping systems.
> Perhaps m->time also? Questionable whether it is useful to log time this record
> was created, when it refers to something much earlier in the BERT case.
>
I agree about m->time. It doesn't seem useful in this case.
But I don't know about m->cpuid. Mixing processor revisions is not
allowed on AMD systems, and I don't know about other vendors. So I'd
leave m->cpuid as global unless there's a strong case otherwise.
> and per-cpu is:
>
> m->cpu = m->extcpu = smp_processor_id();
> m->socketid = cpu_data(m->extcpu).phys_proc_id;
> m->apicid = cpu_data(m->extcpu).initial_apicid;
> m->ppin = cpu_data(m->extcpu).ppin;
>
>> Option #2 can also be used in apei_mce_report_mem_error(), I think.
>
> Agreed.
>
Okay, I'll update that too.
Thanks,
Yazen
next prev parent reply other threads:[~2023-06-23 13:52 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
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 [this message]
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=e6b1af5a-774a-c3ef-223e-4595b7ec532a@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