From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Zachary Amsden <zach@vmware.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
Linus Torvalds <torvalds@osdl.org>, Ingo Molnar <mingo@elte.hu>,
Andi Kleen <ak@suse.de>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Michael A Fetterman <Michael.Fetterman@cl.cam.ac.uk>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: Assignment of GDT entries
Date: Wed, 13 Sep 2006 14:15:09 -0700 [thread overview]
Message-ID: <450874DD.8090109@goop.org> (raw)
In-Reply-To: <4508711B.6060905@vmware.com>
Zachary Amsden wrote:
> I believe 9,10,11 are reserved for future users like yourself or
> expanded TLS segments. I think a bank of 3 TLS segments in the GDT is
> working fine now (does NPTL even use more than one?).
Nope. And there's a comment that wine uses one more. I think the third
is completely unused.
Does this mean that "reserved" is actually synonymous with "unused" in
asm/segment.h?
>> Otherwise line 1 would be ideal for putting 3 TLS, kernel+user
>> code+data and PDA into, thereby making 99.999% of GDT descriptor uses
>> come from one cache line.
>
> That change is visible to userspace, unfortunately.
Don't think it matters much. 32-bit processes on x86-64 seem perfectly
happy with the TLS being in a different place. I think the ABI is
defined in terms of "use the selector for the entry that
set_thread_area/clone returns", and so is not a constant. But I agree
it would be better not to.
Hm, moving user cs/ds would be pretty visible too... Hm, and it would
have a greater chance of breaking stuff if they changed, compared to
moving the TLS...
So is there any reason for "kernel entries start at 12"? If there's no
reason for it, then we can pack everything useful into 1-5.
>> But anyway, what breaks if I put the PDA in 11?
>
> Nothing.
OK then.
J
next prev parent reply other threads:[~2006-09-13 21:15 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-13 18:58 Assignment of GDT entries Jeremy Fitzhardinge
2006-09-13 19:16 ` Arjan van de Ven
2006-09-13 20:00 ` Alan Cox
2006-09-13 20:02 ` Jeremy Fitzhardinge
2006-09-13 20:20 ` Jeremy Fitzhardinge
2006-09-13 20:59 ` Zachary Amsden
2006-09-13 21:15 ` Jeremy Fitzhardinge [this message]
2006-09-13 21:35 ` Alan Cox
2006-09-14 0:25 ` Zachary Amsden
2006-09-14 1:40 ` Stephen Rothwell
2006-09-14 13:03 ` Alan Cox
2006-09-13 19:55 ` linux-os (Dick Johnson)
2006-09-13 20:08 ` Jeremy Fitzhardinge
2006-09-13 20:32 ` linux-os (Dick Johnson)
2006-09-13 21:21 ` Linus Torvalds
2006-09-13 21:47 ` Jeremy Fitzhardinge
2006-09-13 22:05 ` Linus Torvalds
2006-09-13 22:22 ` Jeremy Fitzhardinge
2006-09-14 6:00 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2006-09-14 3:23 Albert Cahalan
2006-09-14 6:11 ` Jeremy Fitzhardinge
2006-09-14 4:06 Albert Cahalan
2006-09-14 4:44 ` Eric W. Biederman
2006-09-14 6:19 ` Albert Cahalan
2006-09-14 6:28 ` Zachary Amsden
2006-09-14 7:12 ` Albert Cahalan
2006-09-14 7:24 ` Zachary Amsden
2006-09-14 6:29 ` Jeremy Fitzhardinge
2006-09-15 7:55 Mikael Pettersson
2006-09-15 8:20 ` Jeremy Fitzhardinge
2006-09-15 8:58 ` Mikael Pettersson
2006-09-15 18:27 ` Jeremy Fitzhardinge
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=450874DD.8090109@goop.org \
--to=jeremy@goop.org \
--cc=Michael.Fetterman@cl.cam.ac.uk \
--cc=ak@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjan@infradead.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@osdl.org \
--cc=zach@vmware.com \
/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