xen-devel
Re: [Xen-devel] Re: [RFC] RAS(Part II)--MCA enalbing in XEN
To: |
Frank van der Linden <Frank.Vanderlinden@xxxxxxx> |
Subject: |
Re: [Xen-devel] Re: [RFC] RAS(Part II)--MCA enalbing in XEN |
From: |
Christoph Egger <Christoph.Egger@xxxxxxx> |
Date: |
Wed, 25 Feb 2009 11:37:00 +0100 |
Cc: |
"xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>, "Ke, Liping" <liping.ke@xxxxxxxxx>, Gavin Maltby <Gavin.Maltby@xxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, "Kleen, Andi" <andi.kleen@xxxxxxxxx> |
Delivery-date: |
Wed, 25 Feb 2009 02:37:38 -0800 |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
In-reply-to: |
<49A44564.3080505@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> <2E9E6F5F5978EF44A8590E339E888CF988279945@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <49A44564.3080505@xxxxxxx> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
User-agent: |
KMail/1.9.7 |
On Tuesday 24 February 2009 20:07:16 Frank van der Linden wrote:
> Kleen, Andi wrote:
> >> MCA information is highly specific to the hardware.
> >
> > Actually Intel has architectural machine checks and except for
> > some optional addon information explicitely marked it's all architectural
> > (as in defined to stay the same going forward)
>
> True, I probably expressed myself poorly here. I meant to say: it's a
> physical hardware error, and in an unmodified virtualized environment
> the information about the physical hardware isn't there.
>
> > For DomU translation of the address is needed, that's correct.
> > For Dom0 logging physical is good because the logging tools
> > might need that.
>
> Right. As far as I understand it, this patch proposes to deliver the
> actual physical information to dom0 via the existing vIRQ mechanism,
> while the vMCE mechanism delivers virtualized info to any guest (both
> dom0 and domU).
The translation is still problematic: What if an error occured which impacts
multiple physical contigous pages ? Translated into guest-physical
address space, they may be non-contigous.
That's why the original design does not support HVM guests unless they
are aware about running in Xen via an PV machine check driver.
Christoph
--
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Karl-Hammerschmidt-Str. 34, 85609 Dornach b. Muenchen
Geschaeftsfuehrer: Jochen Polster, Thomas M. McCoy, Giuliano Meroni
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Re: [Xen-devel] Re: [RFC] RAS(Part II)--MCA enalbing in XEN, (continued)
- Re: [Xen-devel] Re: [RFC] RAS(Part II)--MCA enalbing in XEN, Gavin Maltby
- RE: [Xen-devel] Re: [RFC] RAS(Part II)--MCA enalbing in XEN, Jiang, Yunhong
- Message not available
- RE: [Xen-devel] Re: [RFC] RAS(Part II)--MCA enalbing in XEN, Jiang, Yunhong
- Re: [Xen-devel] Re: [RFC] RAS(Part II)--MCA enalbing in XEN,
Christoph Egger <=
- Message not available
- Re: [Xen-devel] Re: [RFC] RAS(Part II)--MCA enalbing in XEN, Christoph Egger
- RE: [Xen-devel] Re: [RFC] RAS(Part II)--MCA enalbing in XEN, Jiang, Yunhong
|
|
|