From: Jun Sun <jsun@mvista.com>
To: Kumba <kumba@gentoo.org>
Cc: linux-mips@linux-mips.org, jsun@mvista.com
Subject: Re: anybody tried NPTL?
Date: Thu, 5 Aug 2004 10:14:51 -0700 [thread overview]
Message-ID: <20040805101451.A28337@mvista.com> (raw)
In-Reply-To: <411188A8.9040607@gentoo.org>; from kumba@gentoo.org on Wed, Aug 04, 2004 at 09:08:56PM -0400
On Wed, Aug 04, 2004 at 09:08:56PM -0400, Kumba wrote:
> Jun Sun wrote:
>
> > I am looking into porting NPTL to MIPS. Just curious if
> > anybody has tried this before.
> >
> > I notice there was a discussion about the ABI extension
> > for TLS (thread local storage) support. Before that support
> > becomes a reality it seems one can still use NPTL with
> > the help of additional system calls.
> >
> > A rough search of latest glibc source shows there is
> > zero MIPS code for nptl. A couple of other arches
> > are missing as well (such as ARM)
> >
> > Jun
>
> All I've heard about this is that some kernel changes are (still?)
> needed, then just the glibc support along w/ TLS (Maybe compiler support?).
>
TLS support requires ABI change, which involves work in gcc and binutils.
At current stage I think only a few arches have added TLS support.
MIPS is definitely not one of them. Does anybody know about the current
status, for MIPS and other arches?
I think the ABI change and TLS support might take a long time to
be ready. It appears meanwhile NPTL can run without TLS, but would
need a couple of additional system calls that get and set thread
local area.
> I believe I heard reports that the glibc people were looking to
> deprecate linuxthreads within a another release or two (but don't know
> specifics or anything), so it sounds like NPTL should be something to
> get working.
>
That surely puts some urgency on this matter. :)
Jun
next prev parent reply other threads:[~2004-08-05 17:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-04 22:29 anybody tried NPTL? Jun Sun
2004-08-05 1:08 ` Kumba
2004-08-05 17:14 ` Jun Sun [this message]
2004-08-06 2:03 ` Ralf Baechle
2004-08-19 14:17 ` Dominic Sweetman
2004-08-19 14:31 ` Alec Voropay
2004-08-19 14:31 ` Alec Voropay
2004-08-20 6:07 ` Dominic Sweetman
2004-08-20 6:07 ` Dominic Sweetman
2004-08-23 12:28 ` Ralf Baechle
2004-08-23 15:09 ` Alec Voropay
2004-08-23 15:09 ` Alec Voropay
2004-08-23 17:19 ` Ralf Baechle
2004-08-19 16:01 ` David Daney
2004-08-20 6:19 ` Dominic Sweetman
2004-08-19 22:16 ` Jun Sun
2004-08-20 13:46 ` Dominic Sweetman
2004-08-23 13:28 ` Daniel Jacobowitz
2004-08-23 17:12 ` Ralf Baechle
2004-08-23 17:44 ` Daniel Jacobowitz
2004-08-23 19:13 ` Ralf Baechle
2004-08-23 17:37 ` Jun Sun
2004-08-23 19:25 ` Ralf Baechle
2004-08-20 13:12 ` Thiemo Seufer
2004-08-20 16:52 ` Dominic Sweetman
2004-09-01 9:17 ` Richard Sandiford
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=20040805101451.A28337@mvista.com \
--to=jsun@mvista.com \
--cc=kumba@gentoo.org \
--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.