WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] [PATCH] DOM0: Adding MCA Loging support in DOM0

To: Jan Beulich <JBeulich@xxxxxxxxxx>, "Ke, Liping" <liping.ke@xxxxxxxxx>
Subject: RE: [Xen-devel] [PATCH] DOM0: Adding MCA Loging support in DOM0
From: "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>
Date: Tue, 9 Jun 2009 17:30:58 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Delivery-date: Tue, 09 Jun 2009 02:35:06 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4A2E44A20200007800005035@xxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <E2263E4A5B2284449EEBD0AAB751098402CB8B855B@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4A2E44A20200007800005035@xxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acno4w32gRRAgm0jSBSdNscqZvz7IAAARw4Q
Thread-topic: [Xen-devel] [PATCH] DOM0: Adding MCA Loging support in DOM0
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx wrote:
>>>> "Ke, Liping" <liping.ke@xxxxxxxxx> 09.06.09 07:10 >>>
>> This patch is to support MCA info logging in DOM0. When an MCE/CMCI
>> error happens (or by polling), the related error info will be sent
>> to DOM0 by XEN. This patch will help to fetch the xen-logged
>> information by hypercall and then convert XEN-format log into Linux
>> format MCELOG. So we can reuse current available mcelog tools for
>> native Linux now. 
> 
> Could this patch please be re-worked to not needlessly touch non-Xen
> code? This would include a separate config option for the new code,
> while disabling the native sub-options (which at once would avoid the
> hacks you appear to need to make mce_amd.c build).

Jan, I think the native sub-options (X86_MCE_INTEL and X86_MCE_AMD) needs be 
enabled still.
When a MCE happens, and dom0 is effected, that MCE will be injected to dom0 as 
virtual MCE, and that requires to enable these otions.
When a MCE happens and dom0 is not effected, that MCE will be sent to dom0 as 
vIRQ so that dom0 can log that event for analysis.

But yes, maybe following hunk can be done in xen-code to avoid  needless touch.

+
+    /*Register vIRQ handler for MCE LOG processing*/
+#if defined (CONFIG_XEN) && defined(CONFIG_X86_MCE_INTEL)
+    printk(KERN_DEBUG "MCE: bind virq for DOM0 Logging\n");
+    bind_virq_for_mce();
+#endif
+
        return err;

And following code can be removed, although it may cause dom0's needless 
polling.

+#if defined (CONFIG_XEN) && defined(CONFIG_X86_MCE_INTEL)
+static int check_interval = 0; /* disable polling */
+#else
 static int check_interval = 5 * 60; /* 5 minutes */
+#endif
+

Thanks
Yunhong Jiang




> 
> Thanks, Jan
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel