From: David Hopwood <david.nospam.hopwood@blueyonder.co.uk>
To: xen-devel@lists.sourceforge.net
Subject: Re: Re: NPTL/TLS "emulation" idea (fwd)
Date: Thu, 21 Oct 2004 01:56:16 +0100 [thread overview]
Message-ID: <41770930.20502@blueyonder.co.uk> (raw)
In-Reply-To: <20041020182146.GX31909@devserv.devel.redhat.com>
Jakub Jelinek wrote:
> On Wed, Oct 20, 2004 at 06:27:39PM +0100, Keir Fraser wrote:
>>>On Wed, Oct 20, 2004 at 12:55:22PM -0400, Rik van Riel wrote:
>>>
>>>> 4. Provide an alternative libc that does the +ve accesses (which are
>>>> libc private, afaik) in another segment. This does not break the
>>>> ABI for userland programs and -ve accesses aren't that bad when
>>>> there are no +ve accesses in the same segment.
>>>
>>>No, the ABI uses -ve accesses and %gs:0 (4 bytes there), +ve accesses
>>>above +4 are glibc private.
>>
>>Could we duplicate %gs:0 at %gs:-4 and update the ABI? Or is the ABI
>>now set in stone?
>
> The ABI is there for several years, used e.g. in Solaris as well
> and is used already in several libraries, not just glibc.
> The ABI is not going to change for the sake of emulators.
This aspect of the TLS ABI has also been a problem for L4, although for
a different reason (they had already used %gs:0 for something else).
I can't immediately see any solutions arising from that discussion, but
in case it gives anyone else an idea, see
<http://lists.ira.uka.de/pipermail/l4ka/2004-March/000874.html>.
Looks like the same problem is also going to come up for the AMD64 port:
<http://lists.freebsd.org/pipermail/freebsd-threads/2004-March/001850.html>
--
David Hopwood <david.nospam.hopwood@blueyonder.co.uk>
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
next prev parent reply other threads:[~2004-10-21 0:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 13:27 NPTL/TLS "emulation" idea (fwd) Rik van Riel
2004-10-20 14:38 ` Keir Fraser
2004-10-20 14:58 ` Rik van Riel
2004-10-20 15:32 ` Keir Fraser
2004-10-20 16:14 ` Rik van Riel
2004-10-20 16:40 ` Keir Fraser
2004-10-20 16:55 ` Rik van Riel
2004-10-20 17:09 ` Jakub Jelinek
2004-10-20 17:27 ` Keir Fraser
2004-10-20 18:21 ` Jakub Jelinek
2004-10-21 0:56 ` David Hopwood [this message]
2004-10-20 18:04 ` Ian Pratt
-- strict thread matches above, loose matches on Subject: below --
2004-10-20 13:28 Rik van Riel
2004-10-20 14:42 ` Keir Fraser
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=41770930.20502@blueyonder.co.uk \
--to=david.nospam.hopwood@blueyonder.co.uk \
--cc=xen-devel@lists.sourceforge.net \
/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.