Date: Tue, 21 Nov 2000 16:52:08 -0800 From: Julian Elischer <julian@elischer.org> To: Jonathan Lemon <jlemon@flugsvamp.com> Cc: Daniel Eischen <eischen@vigrid.com>, arch@FreeBSD.ORG Subject: Re: Thread-specific data and KSEs Message-ID: <3A1B18B8.37DDA213@elischer.org> References: <Pine.SUN.3.91.1001121184250.29586A-100000@pcnet1.pcnet.com> <20001121175655.T19895@prism.flugsvamp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Jonathan Lemon wrote:
>
> On Tue, Nov 21, 2000 at 06:51:59PM -0500, Daniel Eischen wrote:
> > I'm going to start working on the user-side of the new threads
> > library. I need to be able to quickly get at the current KSE
> > (or perhaps KSEG). Can we define a register on each architecture
> > that should not be used by FreeBSD ABI compliant applications?
> > The register doesn't have to be 32 bits or larger, just large
> > enough to hold the maximum number of KSEs (or KSEGs).
>
> Um. On a i386 I'm not sure this will be practical, there aren't
> a whole lot of architecturally visible registers for use by the
> application.
As I just mentionned in other email, the beauty of the KSE scheme
is that the kernel keeps track of it for you
because the upcalls come back with stacks in different places,
so if you safe the 'current thread' on that stack, you have it where
you need it.
> --
> Jonathan
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-arch" in the body of the message
--
__--_|\ Julian Elischer
/ \ julian@elischer.org
( OZ ) World tour 2000
---> X_.---._/ presently in: Budapest
v
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3A1B18B8.37DDA213>