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: "Kleen, Andi" <andi.kleen@xxxxxxxxx>, "Frank.Vanderlinden@xxxxxxx" <Frank.Vanderlinden@xxxxxxx>
Subject: RE: [Xen-devel] Re: [RFC] RAS(Part II)--MCA enalbing in XEN
From: "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>
Date: Wed, 25 Feb 2009 10:31:08 +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>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, "Ke, Liping" <liping.ke@xxxxxxxxx>
Delivery-date: Tue, 24 Feb 2009 18:33:08 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <2E9E6F5F5978EF44A8590E339E888CF98827996D@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>
References: <C5BF30B3.2C2B%keir.fraser@xxxxxxxxxxxxx> <200902181905.55015.Christoph.Egger@xxxxxxx> <E2263E4A5B2284449EEBD0AAB751098401C7AAC7A0@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <200902191725.32556.Christoph.Egger@xxxxxxx> <E2263E4A5B2284449EEBD0AAB751098401C7AACC2B@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <499F1A1A.2080808@xxxxxxx> <E2263E4A5B2284449EEBD0AAB751098401C7B24F23@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <49A4423F.7070702@xxxxxxx> <2E9E6F5F5978EF44A8590E339E888CF988279945@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <49A44564.3080505@xxxxxxx> <2E9E6F5F5978EF44A8590E339E888CF98827996D@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcmWs0Y2trLdSLxuR4GMIRwEvUQz1QAC2orgAAx0EjA=
Thread-topic: [Xen-devel] Re: [RFC] RAS(Part II)--MCA enalbing in XEN
> That's needed anyways for example to support migration between different
> types of CPUs. The DomU really cannot take a specific CPU type
> for granted or rather has to assume some fallback CPU. Also
> for virtualization
> it's a common case that guests run very old OS, so it's better to give
> them the oldest possible events too.
> 
> So it's generally better to inject generic events, not just
> blindly forward.

Andi, what's the meaning of "generic event"? Do you mean the option 3, i.e. 
some abstract event like page offlie, killing current execution event?
Or you mean translate physical MSR value to guest-aware MSR value?

Thanks
Yunhong Jiang

> 
> Only for Dom0 which does logging the physical hardware needs
> to be described
> correctly.
> 
> -Andi
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel