From: Borislav Petkov <bp@alien8.de>
To: Carlos Bilbao <carlos.bilbao@amd.com>
Cc: tglx@linutronix.de, mingo@redhat.com,
dave.hansen@linux.intel.com, x86@kernel.org,
yazen.ghannam@amd.com, linux-kernel@vger.kernel.org,
linux-edac@vger.kernel.org, bilbao@vt.edu
Subject: Re: [PATCH] x86/mce: Cover grading of AMD machine error checks
Date: Wed, 9 Mar 2022 19:37:33 +0100 [thread overview]
Message-ID: <Yijz7dA1U0AMcYPZ@zn.tnic> (raw)
In-Reply-To: <20220309174107.6113-1-carlos.bilbao@amd.com>
Definitely a step in the right direction.
Now...
On Wed, Mar 09, 2022 at 11:41:07AM -0600, Carlos Bilbao wrote:
> AMD's severity grading covers very few machine errors. In the graded cases
> there are no user-readable messages, complicating debugging of critical
> hardware errors.
That's too generic. What is the actual use case here you're spending all
this time for?
> Fix the above issues extending the current grading logic for AMD with cases
> not previously considered and their corresponding messages.
>
> Signed-off-by: Carlos Bilbao <carlos.bilbao@amd.com>
> ---
> arch/x86/include/asm/mce.h | 6 +
> arch/x86/kernel/cpu/mce/severity.c | 232 +++++++++++++++++++++++++----
> 2 files changed, 205 insertions(+), 33 deletions(-)
Now, looking at the whole thing, AFAICT all you're interested in is
getting some strings out from those error types. But but, we already
have something like that. That's even mentioned in the patch:
> + * Default return values. The poll handler catches these and passes
> + * responsibility of decoding them to EDAC
So there's a big fat module mce_amd.c which does convert MCEs to
strings. So why can't that be used and extended instead of adding more
strings to more places in the kernel?
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2022-03-09 18:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 17:41 [PATCH] x86/mce: Cover grading of AMD machine error checks Carlos Bilbao
2022-03-09 18:37 ` Borislav Petkov [this message]
2022-03-10 18:24 ` Carlos Bilbao
2022-03-10 22:13 ` Borislav Petkov
2022-03-11 14:07 ` Carlos Bilbao
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=Yijz7dA1U0AMcYPZ@zn.tnic \
--to=bp@alien8.de \
--cc=bilbao@vt.edu \
--cc=carlos.bilbao@amd.com \
--cc=dave.hansen@linux.intel.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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