From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Xen-devel <xen-devel@lists.xen.org>
Cc: Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH] x86/pvh: Fix pvh dom0 boot after dab11417d
Date: Tue, 15 Jul 2014 17:57:50 +0200 [thread overview]
Message-ID: <53C54F7E.2050802@citrix.com> (raw)
In-Reply-To: <1405360923-22191-1-git-send-email-andrew.cooper3@citrix.com>
On 14/07/14 20:02, Andrew Cooper wrote:
> Changeset dab11417d
> "x86/HVM: consolidate and sanitize CR4 guest reserved bit determination"
>
> did not take into account the fact that dom0 does not have a cpuid policy. As
> a result, PVH dom0s would be given unexpected #GP faults on boot.
>
> In addition to the restore case (where the toolstack has not had time to load
> a cpuid policy), unconditionally exempt the hardware domain from needing a
> policy.
>
> Reported-by: Roger Pau Monné <roger.pau@citrix.com>
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
> CC: Jan Beulich <JBeulich@suse.com>
Tested-by: Roger Pau Monné <roger.pau@citrix.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2014-07-15 15:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 18:02 [PATCH] x86/pvh: Fix pvh dom0 boot after dab11417d Andrew Cooper
2014-07-15 15:57 ` Roger Pau Monné [this message]
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=53C54F7E.2050802@citrix.com \
--to=roger.pau@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=xen-devel@lists.xen.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).