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/
Home Products Support Community News


RE: [Xen-devel] Re: [PATCH 1/4] CPU online/offline support in Xen

To: Christoph Egger <Christoph.Egger@xxxxxxx>
Subject: RE: [Xen-devel] Re: [PATCH 1/4] CPU online/offline support in Xen
From: "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>
Date: Thu, 18 Sep 2008 11:56:39 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Shan, Haitao" <haitao.shan@xxxxxxxxx>, Gavin Maltby <Gavin.Maltby@xxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, Haitao Shan <maillists.shan@xxxxxxxxx>
Delivery-date: Wed, 17 Sep 2008 20:57:23 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <200809171143.32398.Christoph.Egger@xxxxxxx>
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: <C4EEE682.2707B%keir.fraser@xxxxxxxxxxxxx> <48D0C868.76E4.0078.0@xxxxxxxxxx> <E2263E4A5B2284449EEBD0AAB751098401ABBE479B@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <200809171143.32398.Christoph.Egger@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AckYqfCMO5ppaQXoT/qQARCqfu4JZAAlReQA
Thread-topic: [Xen-devel] Re: [PATCH 1/4] CPU online/offline support in Xen
>> >
>> >Shouldn't this possibly be handled the other way around: If a
>> >recoverable
>> >MCE happened, immediately stop scheduling anything on the affected
>> >CPU(s), until Dom0 tells you otherwise (and of course as
>long as there
>> >remains at least one CPU to run on).
>> Current MCE handling in Xen has no mechanism to achieve this.
>It has since c/s 17968.

Hmm, I think current NMI_MCE_SOFTIRQ can't make sure other guest will not be 
scheduled. Considering there is a schedule softirq already pending on the pCPU, 
other guest may run before the impacted guest. Did I missed anything?

Yunhong Jiang

>AMD Saxony, Dresden, Germany
>Operating System Research Center
>Legal Information:
>AMD Saxony Limited Liability Company & Co. KG
>Sitz (Geschäftsanschrift):
>   Wilschdorfer Landstr. 101, 01109 Dresden, Deutschland
>Registergericht Dresden: HRA 4896
>vertretungsberechtigter Komplementär:
>   AMD Saxony LLC (Sitz Wilmington, Delaware, USA)
>Geschäftsführer der AMD Saxony LLC:
>   Dr. Hans-R. Deppe, Thomas McCoy

Xen-devel mailing list

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