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] machine check support in HVM guests

To: "Keir Fraser" <keir@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] machine check support in HVM guests
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Mon, 27 Nov 2006 14:59:45 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 27 Nov 2006 06:58:28 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C190A85C.51CB%keir@xxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <456B0090.76E4.0078.0@xxxxxxxxxx> <C190A85C.51CB%keir@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>No, I'm not saying that. I was simply expecting that it would be easy to
>fake out a very minimal machine-check emulation where nothing ever goes
>wrong. :-) If that involves GPFing on some MSR accesses, those are easy to
>inject into an HVM guest I believe.

That wasn't my concern, I know that's simple. But the guest may not be
prepared to handle a GP fault here - after all, if CPUID says MCA is
supported, there is no reason the guest should use recovery methods
around accessing the respective MSRs. Likewise, if returning zero, the
guest may BUG(), as it may (validly) assert there's at least one bank of
MSRs supported. And so on...

Jan

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