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


[Xen-devel] mce_wrmsr() and (at least) HVM guests

To: "Liping Ke" <liping.ke@xxxxxxxxx>, "Yunhong Jiang" <yunhong.jiang@xxxxxxxxx>
Subject: [Xen-devel] mce_wrmsr() and (at least) HVM guests
From: "Jan Beulich" <JBeulich@xxxxxxxxxx>
Date: Tue, 01 Dec 2009 11:19:09 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 01 Dec 2009 03:19:32 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
With mce_wrmsr() not permitting to write other than all zeroes or all ones
to MCG_CTL and MCn_CTL, it is not possible for guests to implement
workarounds (see the one in mce_cpu_quirks() which has been present in
Linux versions for a very long time). While one could expect PV guests to
be aware of that (and avoid the workaround), HVM guests clearly can't
be expected to. Thus the question is whether the handling should be
made a little more permissive.

Initially I had thought of just making Xen check whether the bit(s) in
question are also off in the physical MSR, but that would imply that
Xen always has implemented at least all of the workarounds any guest
may know of. I'm not sure I have a good other idea, short of allowing
all writes to succeed.


Xen-devel mailing list

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