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] Re: [patch 0/3]Enable CMCI (Corrected Machine Check Erro

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, "Ke, Liping" <liping.ke@xxxxxxxxx>
Subject: RE: [Xen-devel] Re: [patch 0/3]Enable CMCI (Corrected Machine Check Error Interrupt) for Intel CPUs
From: "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>
Date: Wed, 24 Dec 2008 16:46:00 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 24 Dec 2008 00:47:35 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C5779CE3.20892%keir.fraser@xxxxxxxxxxxxx>
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: <E2263E4A5B2284449EEBD0AAB751098401C4CA8A39@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <C5779CE3.20892%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Aclj6QtzedLMaThJSm+cYEhexWDApwARLffQACOX8KAAB3yQjQAAs9tlACKExYAADbhr/AABSlQg
Thread-topic: [Xen-devel] Re: [patch 0/3]Enable CMCI (Corrected Machine Check Error Interrupt) for Intel CPUs

>-----Original Message-----
>From: Keir Fraser [mailto:keir.fraser@xxxxxxxxxxxxx] 
>Sent: 2008年12月24日 16:02
>To: Jiang, Yunhong; Ke, Liping
>Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
>Subject: Re: [Xen-devel] Re: [patch 0/3]Enable CMCI (Corrected 
>Machine Check Error Interrupt) for Intel CPUs
>
>On 24/12/2008 02:57, "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx> wrote:
>
>> As for your proposal of do it before the stop_machine_run(), 
>it may reduce the
>> window, but still can't eliminate the window of lost CMCI 
>interrupt, unless we
>> do similar thing in the cmci_cpu_down() (i.e. all CPU is 
>irq_disabled before
>> update the CMCI status). It is the same if we pull the 
>notifier chain to Xen.
>> How is your idea?
>
>You only need hardirqs disabled, so rendezvous within an on_each_cpu()
>callback is sufficient for you. You don't need to get intimate with
>stop_machine_run()!

Yes, that's what I mean of "do similar thing in the cmci_cpu_down()". We placed 
it in stop_machine_run() because it has rendezvous all CPU already :$

>
> -- Keir
>
>
>
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>