From: "Naik, Avadhut" <avadnaik@amd.com>
To: Borislav Petkov <bp@alien8.de>, Avadhut Naik <avadhut.naik@amd.com>
Cc: x86@kernel.org, linux-edac@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org, tony.luck@intel.com,
rafael@kernel.org, tglx@linutronix.de, mingo@redhat.com,
rostedt@goodmis.org, lenb@kernel.org, mchehab@kernel.org,
james.morse@arm.com, airlied@gmail.com, yazen.ghannam@amd.com,
john.allen@amd.com
Subject: Re: [PATCH v2 3/4] x86/mce/apei: Handle variable register array size
Date: Wed, 26 Jun 2024 12:28:24 -0500 [thread overview]
Message-ID: <63b6d952-f024-4ed2-baad-819325deb214@amd.com> (raw)
In-Reply-To: <20240626115641.GPZnwB-QEGYCoI_Fv3@fat_crate.local>
On 6/26/2024 06:57, Borislav Petkov wrote:
> On Tue, Jun 25, 2024 at 02:56:23PM -0500, Avadhut Naik wrote:
>> From: Yazen Ghannam <yazen.ghannam@amd.com>
>>
>> ACPI Boot Error Record Table (BERT) is being used by the kernel to
>> report errors that occurred in a previous boot. On some modern AMD
>> systems, these very errors within the BERT are reported through the
>> x86 Common Platform Error Record (CPER) format which consists of one
>> or more Processor Context Information Structures. These context
>> structures provide a starting address and represent an x86 MSR range
>> in which the data constitutes a contiguous set of MSRs starting from,
>> and including the starting address.
>>
>> It's common, for AMD systems that implement this behavior, that the
>> MSR range represents the MCAX register space used for the Scalable MCA
>> feature. The apei_smca_report_x86_error() function decodes and passes
>> this information through the MCE notifier chain. However, this function
>> assumes a fixed register size based on the original HW/FW implementation.
>>
>> This assumption breaks with the addition of two new MCAX registers viz.
>> MCA_SYND1 and MCA_SYND2. These registers are added at the end of the
>> MCAX register space, so they won't be included when decoding the CPER
>> data.
>>
>> Rework apei_smca_report_x86_error() to support a variable register array
>> size. This covers any case where the MSR context information starts at
>> the MCAX address for MCA_STATUS and ends at any other register within
>> the MCAX register space.
>>
>> Add code comments indicating the MCAX register at each offset.
>>
>> [Yazen: Add Avadhut as co-developer for wrapper changes.]
>>
>> Co-developed-by: Avadhut Naik <avadhut.naik@amd.com>
>> Signed-off-by: Avadhut Naik <avadhut.naik@amd.com>
>> Signed-off-by: Yazen Ghannam <yazen.ghannam@amd.com>
>
> This needs Avadhut's SOB after Yazen's.
>
Will do. Will change to the below format:
Co-developed-by: Avadhut Naik <avadhut.naik@amd.com>
Signed-off-by: Yazen Ghannam <yazen.ghannam@amd.com>
Signed-off-by: Avadhut Naik <avadhut.naik@amd.com>
> Touchups ontop:
>
> diff --git a/arch/x86/kernel/cpu/mce/apei.c b/arch/x86/kernel/cpu/mce/apei.c
> index 7a15f0ca1bd1..6bbeb29125a9 100644
> --- a/arch/x86/kernel/cpu/mce/apei.c
> +++ b/arch/x86/kernel/cpu/mce/apei.c
> @@ -69,7 +69,7 @@ EXPORT_SYMBOL_GPL(apei_mce_report_mem_error);
> int apei_smca_report_x86_error(struct cper_ia_proc_ctx *ctx_info, u64 lapic_id)
> {
> const u64 *i_mce = ((const u64 *) (ctx_info + 1));
> - unsigned int cpu, num_registers;
> + unsigned int cpu, num_regs;
> struct mce_hw_err err;
> struct mce *m = &err.m;
>
> @@ -93,10 +93,10 @@ int apei_smca_report_x86_error(struct cper_ia_proc_ctx *ctx_info, u64 lapic_id)
> /*
> * The number of registers in the register array is determined by
> * Register Array Size/8 as defined in UEFI spec v2.8, sec N.2.4.2.2.
> - * Ensure that the array size includes at least 1 register.
> + * Sanity-check registers array size.
> */
> - num_registers = ctx_info->reg_arr_size >> 3;
> - if (!num_registers)
> + num_regs = ctx_info->reg_arr_size >> 3;
> + if (!num_regs)
> return -EINVAL;
>
> mce_setup(m);
> @@ -118,13 +118,12 @@ int apei_smca_report_x86_error(struct cper_ia_proc_ctx *ctx_info, u64 lapic_id)
> /*
> * The SMCA register layout is fixed and includes 16 registers.
> * The end of the array may be variable, but the beginning is known.
> - * Switch on the number of registers. Cap the number of registers to
> - * expected max (15).
> + * Cap the number of registers to expected max (15).
> */
> - if (num_registers > 15)
> - num_registers = 15;
> + if (num_regs > 15)
> + num_regs = 15;
>
> - switch (num_registers) {
> + switch (num_regs) {
> /* MCA_SYND2 */
> case 15:
> err.vi.amd.synd2 = *(i_mce + 14);
>
Will incorporate these.
--
Thanks,
Avadhut Naik
next prev parent reply other threads:[~2024-06-26 17:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 19:56 [PATCH v2 0/4] MCE wrapper and support for new SMCA syndrome MSRs Avadhut Naik
2024-06-25 19:56 ` [PATCH v2 1/4] x86/mce: Add wrapper for struct mce to export vendor specific info Avadhut Naik
2024-06-26 10:44 ` Borislav Petkov
2024-06-26 17:11 ` Luck, Tony
2024-06-26 18:10 ` Borislav Petkov
2024-06-25 19:56 ` [PATCH v2 2/4] x86/mce, EDAC/mce_amd: Add support for new MCA_SYND{1,2} registers Avadhut Naik
2024-06-26 11:10 ` Borislav Petkov
2024-06-26 17:24 ` Naik, Avadhut
2024-06-26 18:18 ` Borislav Petkov
2024-07-09 6:27 ` Naik, Avadhut
2024-07-10 9:38 ` Borislav Petkov
2024-07-10 22:59 ` Naik, Avadhut
2024-06-25 19:56 ` [PATCH v2 3/4] x86/mce/apei: Handle variable register array size Avadhut Naik
2024-06-26 11:57 ` Borislav Petkov
2024-06-26 17:28 ` Naik, Avadhut [this message]
2024-06-25 19:56 ` [PATCH v2 4/4] EDAC/mce_amd: Add support for FRU Text in MCA Avadhut Naik
2024-06-26 12:04 ` Borislav Petkov
2024-06-26 18:00 ` Naik, Avadhut
2024-06-26 18:20 ` Borislav Petkov
2024-06-27 16:20 ` Yazen Ghannam
2024-07-09 6:29 ` Naik, Avadhut
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=63b6d952-f024-4ed2-baad-819325deb214@amd.com \
--to=avadnaik@amd.com \
--cc=airlied@gmail.com \
--cc=avadhut.naik@amd.com \
--cc=bp@alien8.de \
--cc=james.morse@arm.com \
--cc=john.allen@amd.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mingo@redhat.com \
--cc=rafael@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
--cc=yazen.ghannam@amd.com \
/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