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: "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>, "Ke, Liping" <liping.ke@xxxxxxxxx>
Subject: Re: [Xen-devel] Re: [patch 0/3]Enable CMCI (Corrected Machine Check Error Interrupt) for Intel CPUs
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Wed, 24 Dec 2008 14:55:27 +0000
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 24 Dec 2008 06:55:58 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <E2263E4A5B2284449EEBD0AAB751098401C4CA8DC0@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Aclj6QtzedLMaThJSm+cYEhexWDApwARLffQACOX8KAAB3yQjQAAs9tlACKExYAADbhr/AABSlQgAACLzkwACu9HUAABrkD4
Thread-topic: [Xen-devel] Re: [patch 0/3]Enable CMCI (Corrected Machine Check Error Interrupt) for Intel CPUs
User-agent: Microsoft-Entourage/12.15.0.081119
On 24/12/2008 14:51, "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx> wrote:

>>> 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 :$
>> 
>> Yeah, on_each_cpu() rendezvous is pretty cheap. May as well
>> have cleaner
>> partitioned code than avoid an extra rendezvous.
> 
> I'd have a bit clarification here. Simply harirqs disabled in the
> on_each_cpu() is not enough. What we need is, firstly make sure every CPU has
> irq disabled, then every CPU begin update the CMCI status. If this is what you
> mean, we will take a patch for it later.

Every CPU will have IRQs disabled on entry to the on_each_cpu() IPI
function. I couldn't mean much else -- for example, it's not even valid for
the caller of on_each_cpu() to enter it with IRQs disabled.

 -- Keir



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

<Prev in Thread] Current Thread [Next in Thread>