From owner-freebsd-threads@FreeBSD.ORG  Thu Jun 19 21:02:39 2003
Return-Path: <owner-freebsd-threads@FreeBSD.ORG>
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 22BE237B405
	for <threads@freebsd.org>; Thu, 19 Jun 2003 21:02:38 -0700 (PDT)
Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 685F543FAF
	for <threads@freebsd.org>; Thu, 19 Jun 2003 21:02:37 -0700 (PDT)
	(envelope-from eischen@vigrid.com)
Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4])
	by mail.pcnet.com (8.12.8/8.12.1) with ESMTP id h5K42WXh021247;
	Fri, 20 Jun 2003 00:02:33 -0400 (EDT)
Date: Fri, 20 Jun 2003 00:02:32 -0400 (EDT)
From: Daniel Eischen <eischen@vigrid.com>
X-Sender: eischen@pcnet5.pcnet.com
To: Marcel Moolenaar <marcel@xcllnt.net>
In-Reply-To: <20030620034647.GB2260@dhcp01.pn.xcllnt.net>
Message-ID: <Pine.GSO.4.10.10306192358400.19237-100000@pcnet5.pcnet.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: threads@freebsd.org
cc: Julian Elischer <julian@elischer.org>
Subject: Re: Implementing TLS: step 1
X-BeenThere: freebsd-threads@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Threading on FreeBSD <freebsd-threads.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-threads>
List-Post: <mailto:freebsd-threads@freebsd.org>
List-Help: <mailto:freebsd-threads-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jun 2003 04:02:39 -0000

On Thu, 19 Jun 2003, Marcel Moolenaar wrote:

> On Thu, Jun 19, 2003 at 11:39:42PM -0400, Daniel Eischen wrote:
> > 
> > > Q2: Given that libthr has been ported to ia64, what needs to be done
> > >     to port libkse to ia64 (roughtly)?
> > 
> > libpthread/arch/i386/include/ksd.h:
> > libpthread/arch/i386/include/atomic_ops.h
> > libpthread/arch/i386/include/pthread_md.h
> > libpthread/arch/i386/i386:
> 
> No kernel code? Hmmm, looks like something that's worth giving a
> shot. If we have libkse on ia64, we can more easily work on the
> issues related to TLS...

I forgot.  You also need signalcontext() in libc/<arch>/gen/.
All it does is add a signal frame to an existing ucontext.
(It lets the UTS munge a ucontext to add a signal handler
on top of it.)  I assume you already have makecontext().

-- 
Dan Eischen