From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Borislav Petkov <bp@amd64.org>
Cc: "Liu, Jinsong" <jinsong.liu@intel.com>,
"Luck, Tony" <tony.luck@intel.com>,
"'xen-devel@lists.xensource.com'" <xen-devel@lists.xensource.com>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] xen/mce: Add mcelog support for Xen platform
Date: Thu, 31 May 2012 11:30:18 -0400 [thread overview]
Message-ID: <20120531153018.GD9876@phenom.dumpdata.com> (raw)
In-Reply-To: <20120531135009.GC14515@aftab.osrc.amd.com>
On Thu, May 31, 2012 at 03:50:09PM +0200, Borislav Petkov wrote:
> On Thu, May 31, 2012 at 12:57:44PM +0000, Liu, Jinsong wrote:
> > From 1a7951d6ca01d7f2c9dd2bdb6de5f8e7fdcb8bbd Mon Sep 17 00:00:00 2001
> > From: root <root@ljsromley.bj.intel.com>
> > Date: Fri, 1 Jun 2012 03:12:51 +0800
> > Subject: [PATCH 1/2] xen/mce: Add mcelog support for Xen platform
> >
> > When MCA error occurs, it would be handled by Xen hypervisor first,
> > and then the error information would be sent to initial domain for logging.
> >
> > This patch gets error information from Xen hypervisor and convert
> > Xen format error into Linux format mcelog. This logic is basically
> > self-contained, not touching other kernel components.
> >
> > By using tools like mcelog tool users could read specific error information,
> > like what they did under native Linux.
> >
> > To test follow directions outlined in Documentation/acpi/apei/einj.txt
> >
> > Signed-off-by: Ke, Liping <liping.ke@intel.com>
> > Signed-off-by: Jiang, Yunhong <yunhong.jiang@intel.com>
> > Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
> > Signed-off-by: Liu, Jinsong <jinsong.liu@intel.com>
> > ---
> > arch/x86/include/asm/xen/hypercall.h | 8 +
> > arch/x86/kernel/cpu/mcheck/mce.c | 4 +-
> > arch/x86/xen/enlighten.c | 5 +-
> > drivers/xen/Kconfig | 8 +
> > drivers/xen/Makefile | 1 +
> > drivers/xen/mcelog.c | 392 ++++++++++++++++++++++++++++++++++
> > include/linux/miscdevice.h | 1 +
> > include/xen/interface/xen-mca.h | 385 +++++++++++++++++++++++++++++++++
> > 8 files changed, 798 insertions(+), 6 deletions(-)
> > create mode 100644 drivers/xen/mcelog.c
> > create mode 100644 include/xen/interface/xen-mca.h
>
> For the mce bits:
>
> Acked-and-tested-by: Borislav Petkov <borislav.petkov@amd.com>
Sweet. Let me test it on a variety of hardware with Xen and without Xen
with 32/64 variations to double-check.
next prev parent reply other threads:[~2012-05-31 15:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-31 12:57 [PATCH 1/2] xen/mce: Add mcelog support for Xen platform Liu, Jinsong
2012-05-31 13:50 ` Borislav Petkov
2012-05-31 15:30 ` Konrad Rzeszutek Wilk [this message]
2012-05-31 16:11 ` Konrad Rzeszutek Wilk
2012-05-31 17:27 ` Liu, Jinsong
2012-05-31 17:31 ` [Xen-devel] " Konrad Rzeszutek Wilk
2012-05-31 18:08 ` Liu, Jinsong
2012-05-31 18:54 ` Konrad Rzeszutek Wilk
2012-06-01 7:57 ` Liu, Jinsong
2012-06-06 20:55 ` Konrad Rzeszutek Wilk
2012-06-07 6:45 ` Liu, Jinsong
2012-06-07 17:20 ` [Xen-devel] " Konrad Rzeszutek Wilk
2012-06-08 9:27 ` Liu, Jinsong
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=20120531153018.GD9876@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=bp@amd64.org \
--cc=jinsong.liu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.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 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).