From: Kaige Fu <kaige.fu@linux.alibaba.com>
To: linux-edac@vger.kernel.org
Cc: Kaige Fu <kaige.fu@linux.alibaba.com>,
Shannon Zhao <shannon.zhao@linux.alibaba.com>,
Borislav Petkov <bp@alien8.de>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Tony Luck <tony.luck@intel.com>,
James Morse <james.morse@arm.com>,
Robert Richter <rrichter@marvell.com>
Subject: [PATCH] EDAC/mce_amd: Print !SMCA processor warning for 0x19 family
Date: Wed, 28 Apr 2021 11:15:06 +0800 [thread overview]
Message-ID: <93c212e8b182843d0a113cb05571416ba19bc355.1619576976.git.kaige.fu@linux.alibaba.com> (raw)
KVM doesn't enable SMCA for 0x19 family AMD processors.
Consequently, a warning as following will be print when load
edac_mce_amd.ko in a virtual machine.
"Huh? What family is it: 0x19?!"
To make the log more clear, this patch prints !SMCA processor
warning for 0x19 family.
Signed-off-by: Kaige Fu <kaige.fu@linux.alibaba.com>
Cc: Shannon Zhao <shannon.zhao@linux.alibaba.com>
Cc: Borislav Petkov <bp@alien8.de>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: Tony Luck <tony.luck@intel.com>
Cc: James Morse <james.morse@arm.com>
Cc: Robert Richter <rrichter@marvell.com>
Cc: linux-edac@vger.kernel.org
---
drivers/edac/mce_amd.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/edac/mce_amd.c b/drivers/edac/mce_amd.c
index 5dd905a3f30c..0602082c1ef0 100644
--- a/drivers/edac/mce_amd.c
+++ b/drivers/edac/mce_amd.c
@@ -1229,6 +1229,7 @@ static int __init mce_amd_init(void)
case 0x17:
case 0x18:
+ case 0x19:
pr_warn_once("Decoding supported only on Scalable MCA processors.\n");
return -EINVAL;
--
1.8.3.1
next reply other threads:[~2021-04-28 3:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 3:15 Kaige Fu [this message]
2021-04-28 9:06 ` [PATCH] EDAC/mce_amd: Print !SMCA processor warning for 0x19 family Borislav Petkov
2021-04-30 2:47 ` Kaige Fu
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=93c212e8b182843d0a113cb05571416ba19bc355.1619576976.git.kaige.fu@linux.alibaba.com \
--to=kaige.fu@linux.alibaba.com \
--cc=bp@alien8.de \
--cc=james.morse@arm.com \
--cc=linux-edac@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rrichter@marvell.com \
--cc=shannon.zhao@linux.alibaba.com \
--cc=tony.luck@intel.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).