From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org,
jgross@suse.com
Subject: Re: [Xen-devel] [PATCH 4/4] xen/PVH: Remove reserved entry in PVH GDT
Date: Tue, 1 May 2018 08:34:53 -0400 [thread overview]
Message-ID: <5a357f3d-b66e-ca55-0601-18a89b549f4a@oracle.com> (raw)
In-Reply-To: <20180501080009.wnjmno5pietptixo@MacBook-Pro-de-Roger.local>
On 05/01/2018 04:00 AM, Roger Pau Monné wrote:
> On Mon, Apr 30, 2018 at 12:23:39PM -0400, Boris Ostrovsky wrote:
>> And without it we can't use _BOOT_XX macros any longer so define new ones.
>
> Not being that familiar with Linux internals I'm not sure I see the
> benefit of this. Isn't there a risk that some other code is going to
> use the __BOOT_XX defines?
The startup code we are jumping to loads their own GDT and I don't see
any explicit references to segments.
The reason I added this patch was that since we are adding another
segment descriptor (GS) we are now using PVH-specific GDT and so we are
not sharing layout with other code anymore. (Also, the new GS segment
overlaps with __BOOT_TSS so I kind of broke it already there, not
unintentionally).
But if people think I should stick with __BOOT_XX I can drop this patch
(and then probably move GS down one entry).
-boris
next prev parent reply other threads:[~2018-05-01 12:35 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-30 16:23 [PATCH 0/4] PVH GDT fixes and cleanup Boris Ostrovsky
2018-04-30 16:23 ` [PATCH 1/4] xen/PVH: Replace GDT_ENTRY with explicit constant Boris Ostrovsky
2018-04-30 16:57 ` [Xen-devel] " Roger Pau Monné
2018-04-30 18:07 ` Boris Ostrovsky
2018-05-01 7:53 ` Roger Pau Monné
2018-05-01 12:16 ` Boris Ostrovsky
2018-05-01 11:31 ` David Laight
2018-05-01 12:40 ` Boris Ostrovsky
2018-05-02 8:00 ` [Xen-devel] " Jan Beulich
2018-05-02 14:53 ` Boris Ostrovsky
2018-04-30 16:23 ` [PATCH 2/4] xen/PVH: Use proper CS selector in long mode Boris Ostrovsky
2018-05-02 8:05 ` [Xen-devel] " Jan Beulich
2018-05-02 14:57 ` Boris Ostrovsky
2018-05-02 15:00 ` Jan Beulich
2018-05-02 15:08 ` Boris Ostrovsky
2018-05-02 15:09 ` Jan Beulich
2018-05-02 15:28 ` Andrew Cooper
2018-04-30 16:23 ` [PATCH 3/4] xen/PVH: Set up GS segment for stack canary Boris Ostrovsky
2018-05-02 8:16 ` [Xen-devel] " Jan Beulich
2018-05-02 15:00 ` Boris Ostrovsky
2018-05-02 15:01 ` Jan Beulich
2018-05-02 15:22 ` Boris Ostrovsky
2018-05-02 15:41 ` Jan Beulich
2018-05-02 17:29 ` Boris Ostrovsky
2018-05-03 7:35 ` Jan Beulich
2018-04-30 16:23 ` [PATCH 4/4] xen/PVH: Remove reserved entry in PVH GDT Boris Ostrovsky
2018-05-01 8:00 ` [Xen-devel] " Roger Pau Monné
2018-05-01 12:34 ` Boris Ostrovsky [this message]
2018-05-02 8:26 ` Jan Beulich
2018-05-02 15:06 ` Boris Ostrovsky
2018-05-02 15:07 ` Jan Beulich
2018-05-02 8:19 ` 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=5a357f3d-b66e-ca55-0601-18a89b549f4a@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®