From: Andi Kleen <ak@muc.de>
To: Jakub Jelinek <jakub@redhat.com>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sanitize TLS API
Date: 31 Jul 2002 10:52:38 +0200 [thread overview]
Message-ID: <m33cu0l1nt.fsf@averell.firstfloor.org> (raw)
In-Reply-To: Jakub Jelinek's message of "Tue, 30 Jul 2002 22:10:11 +0200"
Jakub Jelinek <jakub@redhat.com> writes:
> Actually, is the clear operation really necessary?
> IMHO the best clear is movw $0x03, %gs, then all accesses through %gs will
> trap. Calling set_thread_area (0, 1); will result in 0xb segment
> acting exactly like %ds or %es.
At least on x86-64 it is useful to have a clear operation, because setting the
thread descriptors adds some cost to the context switch for various reasons.
This way processes you could disable it again when they don't need it anymore.
-Andi
prev parent reply other threads:[~2002-07-31 8:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-30 15:43 [PATCH] sanitize TLS API Christoph Hellwig
2002-07-30 19:00 ` Ingo Molnar
2002-07-30 20:06 ` Jakub Jelinek
2002-07-30 20:16 ` Ingo Molnar
2002-07-31 8:52 ` Andi Kleen [this message]
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=m33cu0l1nt.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=jakub@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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