From: Keir Fraser <keir@xensource.com>
To: Jan Beulich <jbeulich@novell.com>, Keir Fraser <keir@xensource.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: machine check support in HVM guests
Date: Mon, 27 Nov 2006 15:49:15 +0000 [thread overview]
Message-ID: <C190B97B.51E6%keir@xensource.com> (raw)
In-Reply-To: <456B0B71.76E4.0078.0@novell.com>
On 27/11/06 14:59, "Jan Beulich" <jbeulich@novell.com> wrote:
>> 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...
Then we support one bank of MSRs, store writes to those (so the contents can
be read back) but do not act on the writes? I never got the impression
machine check setup was very complicated.
-- Keir
next prev parent reply other threads:[~2006-11-27 15:49 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
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 [this message]
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=C190B97B.51E6%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.