From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Elena Ufimtseva <elena.ufimtseva@oracle.com>,
Ian Campbell <ian.campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Tim Deegan <tim@xen.org>,
xen-devel <xen-devel@lists.xenproject.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [Draft A] Boot ABI for HVM guests without a device-model
Date: Wed, 10 Jun 2015 17:42:21 +0200 [thread overview]
Message-ID: <55785ADD.8000200@citrix.com> (raw)
In-Reply-To: <55785480020000780008312B@mail.emea.novell.com>
Sorry, forgot to reply to one of your chunks.
El 10/06/15 a les 15.15, Jan Beulich ha escrit:
>> * cr0: bit 31 (PG) must be cleared. Bit 0 (PE) must be set. Other bits
>> are all undefined.
>
> I see that grub1 documentation says so, but I doubt this is realistic
> (even less so for cr4 bits): Some of the bits (including ones not
> currently defined) may have a meaning even in non-paged protected
> mode, and the environment should be as completely defined as possible.
> I.e. I think most other bits should be defined to be zero upon handoff.
I think the following is more accurate:
* cr0: bit 0 (PE) and bit 4 (ET) will be set. All the other bits are
cleared.
* cr4: all bits are cleared.
Roger.
next prev parent reply other threads:[~2015-06-10 15:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 12:34 [Draft A] Boot ABI for HVM guests without a device-model Roger Pau Monné
2015-06-10 13:15 ` Jan Beulich
2015-06-10 14:53 ` Roger Pau Monné
2015-06-10 15:53 ` Jan Beulich
2015-06-10 15:42 ` Roger Pau Monné [this message]
2015-06-11 11:01 ` Tim Deegan
2015-06-10 13:18 ` Andrew Cooper
2015-06-10 15:38 ` Roger Pau Monné
2015-06-10 15:57 ` Andrew Cooper
2015-06-11 8:23 ` Roger Pau Monné
2015-06-10 18:55 ` Konrad Rzeszutek Wilk
2015-06-10 21:31 ` Andrew Cooper
2015-06-11 8:31 ` Roger Pau Monné
2015-06-11 7:18 ` Jan Beulich
2015-06-12 13:30 ` Konrad Rzeszutek Wilk
2015-06-11 8:43 ` Roger Pau Monné
2015-06-12 13:23 ` Konrad Rzeszutek Wilk
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=55785ADD.8000200@citrix.com \
--to=roger.pau@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=elena.ufimtseva@oracle.com \
--cc=ian.campbell@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xenproject.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 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.