From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Liu, Jinsong" <jinsong.liu@intel.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] Add mcelog support for xen platform
Date: Fri, 20 Apr 2012 14:40:01 -0400 [thread overview]
Message-ID: <20120420184001.GA447@phenom.dumpdata.com> (raw)
In-Reply-To: <DE8DF0795D48FD4CA783C40EC8292335154EFC@SHSMSX101.ccr.corp.intel.com>
On Thu, Apr 19, 2012 at 01:29:06PM +0000, Liu, Jinsong wrote:
> >From af4467b6cf0104ce98cc160438d865256c7d5561 Mon Sep 17 00:00:00 2001
> From: Liu, Jinsong <jinsong.liu@intel.com>
> Date: Fri, 20 Apr 2012 05:08:38 +0800
> Subject: [PATCH 1/3] 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 dom0 for logging.
How do I test this?
next prev parent reply other threads:[~2012-04-20 18:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 13:29 [PATCH 1/3] Add mcelog support for xen platform Liu, Jinsong
2012-04-20 18:40 ` Konrad Rzeszutek Wilk [this message]
2012-04-20 20:00 ` Liu, Jinsong
2012-04-21 4:14 ` [Xen-devel] " Konrad Rzeszutek Wilk
2012-04-21 10:45 ` Borislav Petkov
2012-04-23 2:18 ` Konrad Rzeszutek Wilk
2012-04-23 6:09 ` Borislav Petkov
2012-04-23 15:06 ` Konrad Rzeszutek Wilk
2012-04-23 15:59 ` Borislav Petkov
2012-04-23 16:23 ` Luck, Tony
2012-04-23 16:54 ` Konrad Rzeszutek Wilk
2012-04-23 16:17 ` Liu, Jinsong
2012-04-23 15:27 ` Luck, Tony
2012-04-23 15:32 ` Konrad Rzeszutek Wilk
2012-04-23 16:17 ` Luck, Tony
2012-04-23 16:51 ` Konrad Rzeszutek Wilk
2012-04-23 15:43 ` Liu, Jinsong
2012-04-23 16:26 ` H. Peter Anvin
2012-04-23 17:05 ` Konrad Rzeszutek Wilk
2012-04-23 17:23 ` H. Peter Anvin
2012-04-23 16:17 ` H. Peter Anvin
2012-04-23 17:03 ` Konrad Rzeszutek Wilk
2012-04-23 17:16 ` H. Peter Anvin
2012-04-24 8:27 ` Andi Kleen
2012-04-25 8:11 ` Ingo Molnar
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=20120420184001.GA447@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=jinsong.liu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--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).