From: Ulrich Drepper <drepper@redhat.com>
To: Andi Kleen <ak@suse.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Better CLONE_SETTLS support for Hammer
Date: Wed, 05 Mar 2003 15:04:07 -0800 [thread overview]
Message-ID: <3E668267.5040203@redhat.com> (raw)
In-Reply-To: <20030305212107.GB7961@wotan.suse.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Andi Kleen wrote:
>>1. every process will already use the prctl(ARCH_SET_FS). We are
>>talking here only about the 2nd thread and later. We need to use
>>prctl(ARCH_SET_FS) for TLS support.
>
>
> Not when you put it into the first four GB. Then you can use the same
> calls as 32bit.
Show me numbers. Or even better: fix the kernel so that I can run it
myself. What is the time difference between using the segment register
switching with all the different allocated thread areas version using wrmsr.
*Iff* using the MSR is slower, as far as I'm concerned the
set_thread_area syscall should complete go away from x86-64. Require
the use of prctl to get and set the base address. Then internally in
the prctl call map it to either the use of a 32 base address segment or
use the MSR.
This way whoever needs a segment base address can preferably allocate it
in the low 4GB, but if it fails the kernel support still work. And with
the same interface. Currently this is not the case and this is not
acceptable.
>>2. May I remind you that you were in the crowd who complained when we
>>requested a dedicated thread register? Yes, I still would prefer that
>>but I have no energy to battle for that.
>
>
> I don't see the connection.
I wouldn't want to either in your position. You caused this whole mess
and now you're not willing to fix it.
- --
- --------------. ,-. 444 Castro Street
Ulrich Drepper \ ,-----------------' \ Mountain View, CA 94041 USA
Red Hat `--' drepper at redhat.com `---------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+ZoJn2ijCOnn/RHQRAtZRAKCFYu1q0IX92o7axPFqK8YuYIdISACfaA1M
TnmREkEevHxAfrhNWYk9uZs=
=ivkl
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-03-05 22:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-05 18:55 Better CLONE_SETTLS support for Hammer Ulrich Drepper
2003-03-05 19:06 ` Andi Kleen
2003-03-05 19:25 ` Ulrich Drepper
2003-03-05 21:19 ` Andi Kleen
2003-03-05 19:32 ` Ulrich Drepper
2003-03-05 21:21 ` Andi Kleen
2003-03-05 23:04 ` Ulrich Drepper [this message]
2003-03-06 1:05 ` Andi Kleen
2003-03-06 3:53 ` Ulrich Drepper
2003-03-06 4:14 ` Ulrich Drepper
2003-03-06 10:27 ` Andi Kleen
2003-03-06 18:58 ` Ulrich Drepper
2003-03-06 19:09 ` Andi Kleen
2003-03-06 2:08 ` Benjamin LaHaise
2003-03-06 3:52 ` Ulrich Drepper
2003-03-06 5:29 ` Benjamin LaHaise
2003-03-06 5:47 ` Ulrich Drepper
2003-03-06 5:33 ` H. Peter Anvin
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=3E668267.5040203@redhat.com \
--to=drepper@redhat.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox