From: Carl van Schaik <carl@ok-labs.com>
To: linux-mips@linux-mips.org
Subject: TLS register for NPTL
Date: Mon, 20 Aug 2007 16:59:01 +1000 [thread overview]
Message-ID: <46C93BB5.9050809@ok-labs.com> (raw)
Hi All,
It seems the rdhwr emulation is used/proposed for accessing the thread
word in NPTL.
I've been reading some of the posts from 2005 about this choice of this
and what I have missed is anyone talking about using the "k0" register
for TLS. It seems logical that the kernel could always restore k0 on
returning to user-land and having k1 only for the last part of returning
to user is sufficient. Any reason why this was not looked at?
regards,
Carl van Schaik
next reply other threads:[~2007-08-20 7:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-20 6:59 Carl van Schaik [this message]
2007-08-20 8:06 ` TLS register for NPTL Thiemo Seufer
2007-08-20 14:54 ` Ralf Baechle
2007-08-21 1:53 ` Carl van Schaik
2007-08-21 12:42 ` Ralf Baechle
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=46C93BB5.9050809@ok-labs.com \
--to=carl@ok-labs.com \
--cc=linux-mips@linux-mips.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.