From owner-freebsd-current@FreeBSD.ORG Mon Jun 7 15:33:42 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5A9E516A4CE for ; Mon, 7 Jun 2004 15:33:42 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0713E43D5A for ; Mon, 7 Jun 2004 15:33:42 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from freebsd.org (junior-wifi.samsco.home [192.168.0.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i57FfDEn048686; Mon, 7 Jun 2004 09:41:13 -0600 (MDT) (envelope-from scottl@freebsd.org) Message-ID: <40C48AB3.50705@freebsd.org> Date: Mon, 07 Jun 2004 09:33:07 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040304 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Doug Rabson References: <200406071011.01370.dfr@nlsystems.com> In-Reply-To: <200406071011.01370.dfr@nlsystems.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-current@freebsd.org Subject: Re: HEADS UP! KSE needs more attention X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jun 2004 15:33:42 -0000 Doug Rabson wrote: > On Sunday 06 June 2004 20:55, Daniel Eischen wrote: > >>On Sun, 6 Jun 2004, Scott Long wrote: >> >>>All, >>> >>>We are about 4-6 weeks away from starting the 5.3 release cycle. >>>As it stands, KSE still only works reliably on i386. There are >>>reports of significant instability on amd64, and it doesn't work at >>>all on alpha and sparc64. I'm willing to drop the alpha >>>requirement and maybe even the sparc64 requirement, but there >>>absolutely will not be a 5.3 until amd64 is solid. Please contact >>>myself, Dan Eischen, and David Xu if you are interested in helping >>>out. >> >>amd64 looks to be a problem in readline which doesn't seem >>to redispatch signal handlers with SA_SIGINFO arguments. >> >>David also has patches for debugging support at: >> >> http://people.freebsd.org/~davidxu/kse/dbg/ >> >>Doug Rabson also has basic TLS support working in perforce. >>It'd be nice to get TLS and debugging in before 5.3-release. > > > I'll probably try to commit some kind of TLS support into current in the > next couple of weeks. Its likely to only support i386 and will be > stubbed out for other platforms. Right now, I'm just waiting for some > kind of feedback from an nvidia developer whos testing it. I'm happy to see that it's gotten this far along, but it needs to be available on all tier-1 platforms when it goes in. For the sake of argument, we'll call that amd64 and possibly sparc64. My understanding is that amd64 should be very similar to i386, yes? Please let me know what kind of help you need with getting this done. Scott