From: Paolo Bonzini <pbonzini@redhat.com>
To: Andy Lutomirski <luto@amacapital.net>,
Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Andy Lutomirski <luto@kernel.org>, X86 ML <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Borislav Petkov <bp@alien8.de>, kvm list <kvm@vger.kernel.org>,
xen-devel <Xen-devel@lists.xen.org>
Subject: Re: [Xen-devel] Does __KERNEL_DS serve a purpose?
Date: Fri, 8 Apr 2016 19:12:33 +0200 [thread overview]
Message-ID: <5707E681.7040202@redhat.com> (raw)
In-Reply-To: <CALCETrXeU7oi9F+k+mrjV=jo9TW9ic8tOA094j9mbyrX12Jazw@mail.gmail.com>
On 08/04/2016 18:00, Andy Lutomirski wrote:
> But %ss can be loaded with 0 on 64-bit kernels. (I assume that
> loading 0 into %ss sets SS.DPL to 0 if done at CPL0, but I'm vague on
> this, since it only really matters to hypervisor code AFAIK.)
It's even simpler, unless CPL=0 SS cannot be loaded with 0 while in a
64-bit code segment (SS can never be loaded with 0 if you're not in a
64-bit code segment).
Thus indeed SS=0 implies SS.DPL=0 on 64-bit kernels.
Paolo
> 32-bit kernels need __KERNEL_DS, I think.
next prev parent reply other threads:[~2016-04-08 17:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-08 0:24 Does __KERNEL_DS serve a purpose? Andy Lutomirski
2016-04-08 8:01 ` Andrew Cooper
2016-04-08 8:01 ` [Xen-devel] " Andrew Cooper
2016-04-08 16:00 ` Andy Lutomirski
2016-04-08 16:00 ` [Xen-devel] " Andy Lutomirski
2016-04-08 17:12 ` Paolo Bonzini
2016-04-08 17:12 ` Paolo Bonzini [this message]
2016-04-08 22:06 ` [Xen-devel] " Andy Lutomirski
2016-04-08 22:32 ` Andrew Cooper
2016-04-08 22:32 ` [Xen-devel] " Andrew Cooper
2016-04-08 22:06 ` Andy Lutomirski
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=5707E681.7040202@redhat.com \
--to=pbonzini@redhat.com \
--cc=Xen-devel@lists.xen.org \
--cc=andrew.cooper3@citrix.com \
--cc=bp@alien8.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=luto@kernel.org \
--cc=x86@kernel.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.