Date: Tue, 21 Nov 2000 19:58:36 -0500 (EST) From: Daniel Eischen <eischen@vigrid.com> To: Jonathan Lemon <jlemon@flugsvamp.com> Cc: arch@FreeBSD.ORG Subject: Re: Thread-specific data and KSEs Message-ID: <Pine.SUN.3.91.1001121195753.8183B-100000@pcnet1.pcnet.com> In-Reply-To: <20001121175655.T19895@prism.flugsvamp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 21 Nov 2000, 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.
Why can't we use a segment register?
--
"Some may prefer open source, but me, I prefer open bar."
-- Spencer F. Katt
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?Pine.SUN.3.91.1001121195753.8183B-100000>