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: [RFC] RAS(Part II)--MCA enalbing in XEN

To: "Frank.Vanderlinden@xxxxxxx" <Frank.Vanderlinden@xxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Subject: RE: [Xen-devel] Re: [RFC] RAS(Part II)--MCA enalbing in XEN
From: "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>
Date: Tue, 17 Feb 2009 14:44:07 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: Gavin Maltby <Gavin.Maltby@xxxxxxx>, Christoph Egger <Christoph.Egger@xxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Ke, Liping" <liping.ke@xxxxxxxxx>
Delivery-date: Mon, 16 Feb 2009 22:44:51 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <499A500A.6000301@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: <C5BF30B3.2C2B%keir.fraser@xxxxxxxxxxxxx> <4999A94D.5020500@xxxxxxx> <499A500A.6000301@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcmQw6EGuWDZy37MQ3CGt5MuA1hGLAAByZcw
Thread-topic: [Xen-devel] Re: [RFC] RAS(Part II)--MCA enalbing in XEN
 

>-----Original Message-----
>From: Frank.Vanderlinden@xxxxxxx [mailto:Frank.Vanderlinden@xxxxxxx] 
>Sent: 2009年2月17日 13:50
>To: Keir Fraser
>Cc: Gavin Maltby; Christoph Egger; 
>xen-devel@xxxxxxxxxxxxxxxxxxx; Jiang, Yunhong; Ke, Liping
>Subject: Re: [Xen-devel] Re: [RFC] RAS(Part II)--MCA enalbing in XEN
>
>I should probably clarify myself, since I may have created one wrong 
>impression: I don't object to the parts of the Intel code where the 
>hypervisor does more of the initial work (like is also done in 
>the page 
>offline code); it can be critical that this work is done quickly, and 
>the hypervisor is the only place that has both the information and the 
>means to do it.

Yes, agree.

>
>So, doing some more work there in some cases is probably the 
>best thing 
>to do, even though there is natural resistance to adding more code to 
>the hypervisor.

We all agree to keep HV less code, and we will try to reduce the LOC in next 
round patch.

>
>The main thing that I don't quite understand the benefits of 
>is the vMCE 
>code, which is why I asked if there are examples of where that 
>approach 
>would work better.

Please see my mail I just sent out, you can also refer to 
http://lists.xensource.com/archives/html/xen-devel/2008-12/msg00643.html. 

Thanks
Yunhong Jiang

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