From owner-freebsd-threads@FreeBSD.ORG Tue Aug 5 14:00:12 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D778E37B401; Tue, 5 Aug 2003 14:00:12 -0700 (PDT) Received: from ns1.xcllnt.net (209-128-86-226.BAYAREA.NET [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1511B43F3F; Tue, 5 Aug 2003 14:00:12 -0700 (PDT) (envelope-from marcel@xcllnt.net) Received: from athlon.pn.xcllnt.net (athlon.pn.xcllnt.net [192.168.4.3]) by ns1.xcllnt.net (8.12.9/8.12.9) with ESMTP id h75L0BwO033189; Tue, 5 Aug 2003 14:00:11 -0700 (PDT) (envelope-from marcel@piii.pn.xcllnt.net) Received: from athlon.pn.xcllnt.net (localhost [127.0.0.1]) by athlon.pn.xcllnt.net (8.12.9/8.12.9) with ESMTP id h75L0BYn001000; Tue, 5 Aug 2003 14:00:11 -0700 (PDT) (envelope-from marcel@athlon.pn.xcllnt.net) Received: (from marcel@localhost) by athlon.pn.xcllnt.net (8.12.9/8.12.9/Submit) id h75L0BAU000999; Tue, 5 Aug 2003 14:00:11 -0700 (PDT) (envelope-from marcel) Date: Tue, 5 Aug 2003 14:00:11 -0700 From: Marcel Moolenaar To: deischen@freebsd.org Message-ID: <20030805210011.GB879@athlon.pn.xcllnt.net> References: <20030805203213.GA879@athlon.pn.xcllnt.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.4i cc: threads@freebsd.org Subject: Re: Good news: KSE on ia64 is starting to work X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Aug 2003 21:00:13 -0000 On Tue, Aug 05, 2003 at 04:43:00PM -0400, Daniel Eischen wrote: > > In struct ia64_tp we define tp_tls as an array of char. If we > > define it as an array of long double we automaticly have 16-byte > > alignment of the static TLS, struct ia64_tp, struct tcb and > > struct kcb. Allocating the TCB will then automaticly ensure that > > the static TLS is properly aligned. I'm currently testing with > > the following (re)definition of struct ia64_tp: > > > > struct ia64_tp { > > struct tdv *tp_tdv; /* dynamic TLS */ > > struct tcb *tp_self; > > long double tp_tls[0]; /* static TLS */ > > }; > > Sure; that was merely a placeholder so one (you) could replace > it with whatever is needed. I assume this (static TLS) will > have some predetermined size... It's a runtime constant yes. We'll know the size of the static TLS when we initialize libkse/libpthread and TLS support has been added. I expect that kcb_faketcb doesn't need any TLS, because it's not used for running user code, just an internal "doohicky", right? BTW: Feel free to commit your patch at your earliest convenience (with or without the change described above). I see a slight regression after applying the patch, but much rather see it committed than having to work with a large patch... -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net