[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <cf9ef89c-ca91-476a-895d-2af50616242f@linux.alibaba.com>
Date: Sat, 1 Mar 2025 14:16:12 +0800
From: Shuai Xue <xueshuai@...ux.alibaba.com>
To: Borislav Petkov <bp@...en8.de>
Cc: tony.luck@...el.com, nao.horiguchi@...il.com, tglx@...utronix.de,
mingo@...hat.com, dave.hansen@...ux.intel.com, x86@...nel.org,
hpa@...or.com, linmiaohe@...wei.com, akpm@...ux-foundation.org,
peterz@...radead.org, jpoimboe@...nel.org, linux-edac@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
baolin.wang@...ux.alibaba.com, tianruidong@...ux.alibaba.com
Subject: Re: [PATCH v2 2/5] x86/mce: dump error msg from severities
在 2025/2/28 20:37, Borislav Petkov 写道:
> On Mon, Feb 17, 2025 at 02:33:32PM +0800, Shuai Xue wrote:
>> The message in severities is useful for identifying the type of MCE that
>> has occurred; dump it if it is valid.
>
> Needs more explanation as to what "useful" means. We already log and report
> MCEs in gazillion ways.
>
You are right.
While MCE information is indeed decoded by the EDAC and APEI drivers,
the decoding is limited to the interpretation of hardware registers
and lacks the contextual details of the error.
For instance, it does not specify whether the error occurred in the
context of IN_KERNEL or IN_KERNEL_RECOV, which are crucial for
understanding the error's circumstances.
For the regression cases (copy from user) in Patch 3, an error message
"mce: Action required: data load in error recoverable area of kernel"
will be added if this patch is applied.
I could add more explanations in next version if you have no objection.
Thanks.
Shuai
Powered by blists - more mailing lists