From owner-freebsd-threads@FreeBSD.ORG Thu Apr 17 23:04:35 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 931) id 762EB37B401; Thu, 17 Apr 2003 23:04:35 -0700 (PDT) Date: Fri, 18 Apr 2003 01:04:35 -0500 From: Juli Mallett To: David Xu Message-ID: <20030418010435.A6251@FreeBSD.org> References: <002f01c3056f$6d9b7840$f001a8c0@davidw2k> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <002f01c3056f$6d9b7840$f001a8c0@davidw2k>; from davidxu@freebsd.org on Fri, Apr 18, 2003 at 01:57:43PM +0800 Organisation: The FreeBSD Project X-Alternate-Addresses: , , , , X-Towel: Yes X-Negacore: Yes X-Title: Code Maven X-Authentication-Warning: localhost: juli pwned teh intarweb cc: Daniel Eischen cc: freebsd-threads@freebsd.org Subject: Re: libpthread patch 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: Fri, 18 Apr 2003 06:04:35 -0000 * De: David Xu [ Data: 2003-04-18 ] [ Subjecte: Re: libpthread patch ] > > There are a few issues we've got to go over, as well as > > looking closely at any locking order problems. > > > I have ever tried to port some kernel code to userland (e.g > mutex and witness), but now they were left there for > several days without be touched. This seems like overkill, in fact, it is by definition. If you want some primitive private-locks-only mutex tracing/auditing, I've done a bit of that and could give you some hints. Using the casuptr facility introduced by thr may be a good idea, no? It is known to work, and is relatively un-complex? Or am I missing something? -- juli mallett. email: jmallett@freebsd.org; aim: bsdflata; efnet: juli;