From: Carlos Bilbao <carlos.bilbao@amd.com>
To: <bp@alien8.de>
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>,
Carlos Bilbao <carlos.bilbao@amd.com>
Subject: [PATCH 0/2] x86/mce: Grade new machine errors for AMD MCEs and include messages for panic cases
Date: Mon, 28 Mar 2022 08:41:30 -0500 [thread overview]
Message-ID: <20220328134131.736572-1-carlos.bilbao@amd.com> (raw)
This patchset includes grading of new types of machine errors on AMD's MCE
grading logic mce_severity_amd(), which helps the MCE handler determine
what actions to take. If the error is graded as a PANIC, the EDAC driver
will not decode; so we also include new error messages to describe the MCE
and help debugging critical errors.
Carlos Bilbao (2):
x86/mce: Extend AMD severity grading function with new types of errors
x86/mce: Add messages to describe panic machine errors on AMD's MCEs grading
arch/x86/include/asm/mce.h | 6 +
arch/x86/kernel/cpu/mce/severity.c | 203 ++++++++++++++++++++++++-----
2 files changed, 174 insertions(+), 35 deletions(-)
--
2.27.0
next reply other threads:[~2022-03-28 13:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 13:41 Carlos Bilbao [this message]
2022-03-28 13:41 ` [PATCH 1/2] x86/mce: Extend AMD severity grading function with new types of errors Carlos Bilbao
2022-03-30 20:02 ` Yazen Ghannam
2022-03-31 14:41 ` Carlos Bilbao
2022-03-28 13:41 ` [PATCH 2/2] x86/mce: Add messages to describe panic machine errors on AMD's MCEs grading Carlos Bilbao
2022-03-28 13:55 ` [PATCH 0/2] x86/mce: Grade new machine errors for AMD MCEs and include messages for panic cases Borislav Petkov
2022-03-28 13:57 ` Carlos Bilbao
2022-03-28 14:04 ` Borislav Petkov
2022-03-28 14:09 ` Carlos Bilbao
2022-03-28 14:16 ` Borislav Petkov
-- strict thread matches above, loose matches on Subject: below --
2022-03-11 16:51 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=20220328134131.736572-1-carlos.bilbao@amd.com \
--to=carlos.bilbao@amd.com \
--cc=bilbao@vt.edu \
--cc=bp@alien8.de \
--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;
as well as URLs for NNTP newsgroup(s).