From: Jakub Jelinek <jakub@redhat.com>
To: Rik van Riel <riel@redhat.com>
Cc: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>,
xen-devel@lists.sourceforge.net, jakub@redhat.com,
roland@redhat.com
Subject: Re: Re: NPTL/TLS "emulation" idea (fwd)
Date: Wed, 20 Oct 2004 13:09:25 -0400 [thread overview]
Message-ID: <20041020170925.GW31909@devserv.devel.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0410201254160.21939-100000@chimarrao.boston.redhat.com>
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.
Jakub
-------------------------------------------------------
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-20 17:09 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 [this message]
2004-10-20 17:27 ` Keir Fraser
2004-10-20 18:21 ` Jakub Jelinek
2004-10-21 0:56 ` David Hopwood
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=20041020170925.GW31909@devserv.devel.redhat.com \
--to=jakub@redhat.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=riel@redhat.com \
--cc=roland@redhat.com \
--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.