From owner-freebsd-arch Tue Nov 21 15:57:40 2000 Delivered-To: freebsd-arch@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id EB85037B4CF for ; Tue, 21 Nov 2000 15:57:38 -0800 (PST) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id eALNutZ32181; Tue, 21 Nov 2000 17:56:55 -0600 (CST) (envelope-from jlemon) Date: Tue, 21 Nov 2000 17:56:55 -0600 From: Jonathan Lemon To: Daniel Eischen Cc: arch@FreeBSD.ORG Subject: Re: Thread-specific data and KSEs Message-ID: <20001121175655.T19895@prism.flugsvamp.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message