From: Yazen Ghannam <yazen.ghannam@amd.com>
To: <linux-edac@vger.kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <tony.luck@intel.com>,
<x86@kernel.org>, <Smita.KoralahalliChannabasappa@amd.com>,
Yazen Ghannam <yazen.ghannam@amd.com>
Subject: [PATCH 0/3] New SMCA Syndrome registers and FRU Text feature
Date: Mon, 18 Apr 2022 17:40:07 +0000 [thread overview]
Message-ID: <20220418174010.330559-1-yazen.ghannam@amd.com> (raw)
Hello,
This patchset adds support for two new "syndrome" registers used in
future AMD Scalable MCA (SMCA) systems and also a new "FRU Text in MCA"
feature that uses these new registers.
Patch 1 adds support for the new registers. They are read/printed
wherever the existing MCA_SYND register is used.
Patch 2 updates the function that pulls MCA information from UEFI x86
Common Platform Error Records (CPERs) to handle systems that support the
new registers.
Patch 3 adds support to the AMD MCE decoder module to detect and use the
"FRU Text in MCA" feature which leverages the new registers.
Thanks,
Yazen
Yazen Ghannam (3):
x86/MCE, EDAC/mce_amd: Add support for new MCA_SYND{1,2} registers
x86/MCE/APEI: Handle variable register array size
EDAC/mce_amd: Add support for FRU Text in MCA
arch/x86/include/asm/mce.h | 5 +++
arch/x86/include/uapi/asm/mce.h | 2 +
arch/x86/kernel/cpu/mce/amd.c | 5 ++-
arch/x86/kernel/cpu/mce/apei.c | 73 ++++++++++++++++++++++++++-------
arch/x86/kernel/cpu/mce/core.c | 9 +++-
drivers/edac/mce_amd.c | 24 ++++++++---
include/trace/events/mce.h | 7 +++-
7 files changed, 103 insertions(+), 22 deletions(-)
--
2.25.1
next reply other threads:[~2022-04-18 17:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 17:40 Yazen Ghannam [this message]
2022-04-18 17:44 [PATCH 0/3] New SMCA Syndrome registers and FRU Text feature Yazen Ghannam
2022-06-10 16:29 ` 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=20220418174010.330559-1-yazen.ghannam@amd.com \
--to=yazen.ghannam@amd.com \
--cc=Smita.KoralahalliChannabasappa@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;
as well as URLs for NNTP newsgroup(s).