From owner-freebsd-arch Tue Nov 21 17: 1:23 2000 Delivered-To: freebsd-arch@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id CF4AD37B4D7 for ; Tue, 21 Nov 2000 17:01:20 -0800 (PST) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id TAA09651; Tue, 21 Nov 2000 19:58:36 -0500 (EST) Date: Tue, 21 Nov 2000 19:58:36 -0500 (EST) From: Daniel Eischen To: Jonathan Lemon Cc: arch@FreeBSD.ORG Subject: Re: Thread-specific data and KSEs In-Reply-To: <20001121175655.T19895@prism.flugsvamp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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