From: Keir Fraser <keir@xensource.com>
To: Jan Beulich <jbeulich@novell.com>, xen-devel@lists.xensource.com
Subject: Re: machine check support in HVM guests
Date: Mon, 27 Nov 2006 13:27:22 +0000 [thread overview]
Message-ID: <C190983A.51BC%keir@xensource.com> (raw)
In-Reply-To: <456AE849.76E4.0078.0@novell.com>
On 27/11/06 12:29, "Jan Beulich" <jbeulich@novell.com> wrote:
> Neither SVM nor VMX suppress CPUID[1].EDX.MC{E,A}, but there also is no
> virtualization of the respective MSRs. Since the latter seems to have at best
> marginal usefulness, shouldn't CPUID be respectively updated?
Virtualisation of CPUID is currently back-to-front imo. We should be
supplying an entirely fake CPUID space, filled in with native info only in
places where that makes sense. Instead we supply native info, replaced with
virtualised alternatives where that turns out to be needed. This, for
example, means we cannot guarantee to support HVM guests with current Xen on
future processors. They may extend the CPUID space in a way that current Xen
does not understand and cause guests to try to use features that Xen does
not virtualise or emulate.
For your specific question, MCE/MCA used to be removed but 64-bit Windows
requires this feature to be available (not sure if it's just for WHQL
though). So we should emulate some basic MC support; enough to accept and
discard MSR programming at least.
-- Keir
next prev parent reply other threads:[~2006-11-27 13:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-27 12:29 machine check support in HVM guests Jan Beulich
2006-11-27 13:22 ` Petersson, Mats
2006-11-27 13:27 ` Keir Fraser [this message]
2006-11-27 14:10 ` Jan Beulich
2006-11-27 14:13 ` Jan Beulich
2006-11-27 14:36 ` Keir Fraser
2006-11-27 14:42 ` Petersson, Mats
2006-11-27 14:59 ` Jan Beulich
2006-11-27 15:49 ` Keir Fraser
2006-11-27 16:01 ` Jan Beulich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C190983A.51BC%keir@xensource.com \
--to=keir@xensource.com \
--cc=jbeulich@novell.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.