From: "Jan Beulich" <JBeulich@suse.com>
To: Roger Pau Monne <roger.pau@citrix.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xenproject.org, David Vrabel <david.vrabel@citrix.com>
Subject: Re: [PATCH v3] docs: add PVH specification
Date: Mon, 22 Sep 2014 12:16:26 +0100 [thread overview]
Message-ID: <5420212A0200007800036DA3@mail.emea.novell.com> (raw)
In-Reply-To: <20140920191510.GA2882@laptop.dumpdata.com>
>>> On 20.09.14 at 21:15, <konrad.wilk@oracle.com> wrote:
> On Thu, Sep 18, 2014 at 07:19:24PM +0200, Roger Pau Monne wrote:
>> +All the segments selectors are set with a flat base at zero.
>> +
>> +The `cs` segment selector attributes are set to 0x0a09b, which describes an
>> +executable and readable code segment only accessible by the most privileged
>> +level. The segment is also set as a 64-bit code segment (`L` flag set, `D` flag
>> +unset).
>> +
>> +The remaining segment selectors (`ds`, `ss`, `es`, `fs` and `gs`) are all set
>> +to the same values. The attributes are set to 0x0c093, which implies a read and
>> +write data segment only accessible by the most privileged level.
>
> I think the SS, ES, FS, GS are set to the null selector in 64-bit mode.
Right - with their hidden portions set to what is being said in
Roger's description.
Jan
next prev parent reply other threads:[~2014-09-22 11:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 17:19 [PATCH v3] docs: add PVH specification Roger Pau Monne
2014-09-20 19:15 ` Konrad Rzeszutek Wilk
2014-09-22 11:16 ` Jan Beulich [this message]
2014-09-22 13:40 ` Konrad Rzeszutek Wilk
2014-09-22 11:36 ` Roger Pau Monné
2014-09-22 14:02 ` Konrad Rzeszutek Wilk
2014-09-22 14:08 ` Jan Beulich
2014-09-23 0:38 ` Mukesh Rathor
2014-09-23 13:16 ` Jan Beulich
2014-09-26 0:00 ` Mukesh Rathor
2014-09-26 6:32 ` Jan Beulich
2014-09-29 17:38 ` Roger Pau Monné
2014-09-29 17:45 ` David Vrabel
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=5420212A0200007800036DA3@mail.emea.novell.com \
--to=jbeulich@suse.com \
--cc=david.vrabel@citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=roger.pau@citrix.com \
--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 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).