From: Christoph Egger <Christoph.Egger@amd.com>
To: xen-devel@lists.xensource.com
Subject: [PATCH] xen: prettify mce output
Date: Tue, 21 Jul 2009 16:56:26 +0200 [thread overview]
Message-ID: <200907211656.26519.Christoph.Egger@amd.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 389 bytes --]
Hi!
Attached patch prettifies Xen's mce output.
Signed-off-by: Christoph Egger <Christoph.Egger@amd.com>
--
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Karl-Hammerschmidt-Str. 34, 85609 Dornach b. Muenchen
Geschaeftsfuehrer: Thomas M. McCoy, Giuliano Meroni
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632
[-- Attachment #2: xen_mce.diff --]
[-- Type: text/x-diff, Size: 979 bytes --]
diff -r 534d3716bbbe xen/arch/x86/cpu/mcheck/mce.c
--- a/xen/arch/x86/cpu/mcheck/mce.c Tue Jul 21 12:06:52 2009 +0100
+++ b/xen/arch/x86/cpu/mcheck/mce.c Tue Jul 21 16:56:07 2009 +0200
@@ -798,7 +798,7 @@ int mce_wrmsr(u32 msr, u64 value)
case MSR_IA32_MCG_CTL:
if ( value && (value + 1) )
{
- gdprintk(XENLOG_WARNING, "MCE: value written to MCG_CTL"
+ gdprintk(XENLOG_WARNING, "MCE: value written to MCG_CTL "
"should be all 0s or 1s\n");
ret = -1;
break;
@@ -847,7 +847,7 @@ int mce_wrmsr(u32 msr, u64 value)
case MSR_IA32_MC0_CTL:
if ( value && (value + 1) )
{
- gdprintk(XENLOG_WARNING, "MCE: value written to MC%u_CTL"
+ gdprintk(XENLOG_WARNING, "MCE: value written to MC%u_CTL "
"should be all 0s or 1s (is %"PRIx64")\n",
bank, value);
ret = -1;
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
reply other threads:[~2009-07-21 14:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200907211656.26519.Christoph.Egger@amd.com \
--to=christoph.egger@amd.com \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.