[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DE8DF0795D48FD4CA783C40EC8292335159293@SHSMSX101.ccr.corp.intel.com>
Date: Fri, 20 Apr 2012 20:00:53 +0000
From: "Liu, Jinsong" <jinsong.liu@...el.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
CC: "xen-devel@...ts.xensource.com" <xen-devel@...ts.xensource.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 1/3] Add mcelog support for xen platform
Konrad Rzeszutek Wilk wrote:
> 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@...el.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?
It can be tested by EINJ tool to inject an memory error, and by mcelog tool to read error info, basically it need:
1. enable einj tools: load EINJ kernel module and mount debugfs;
2. set error type
# cat available_error_type (depend on your bios)
0x00000002 Processor Uncorrectable non-fatal
0x00000008 Memory Correctable
0x00000010 Memory Uncorrectable non-fatal
# echo 0x8 > error_type
3. find a proper physical address for injection (usually use a free page like xen heap page)
4. set the injection address and mask
# echo address > param1
# echo mask > param2
5. inject error
# echo 1 > error_inject
6. use mcelog tool to read error info
Thanks,
Jinsong--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists