From owner-p4-projects@FreeBSD.ORG Tue Apr 25 15:12:59 2006 Return-Path: X-Original-To: p4-projects@freebsd.org Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id 9806516A468; Tue, 25 Apr 2006 15:12:59 +0000 (UTC) X-Original-To: perforce@freebsd.org Delivered-To: perforce@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0402816A406 for ; Tue, 25 Apr 2006 15:12:59 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 05E3543D46 for ; Tue, 25 Apr 2006 15:12:57 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k3PFCsRc061673; Tue, 25 Apr 2006 11:12:55 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: John Birrell Date: Tue, 25 Apr 2006 10:59:35 -0400 User-Agent: KMail/1.9.1 References: <200604241913.k3OJDEAq055317@repoman.freebsd.org> <200604241748.59461.jhb@freebsd.org> <20060424220405.GA62694@what-creek.com> In-Reply-To: <20060424220405.GA62694@what-creek.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200604251059.36556.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1425/Tue Apr 25 08:09:41 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.1 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: Perforce Change Reviews Subject: Re: PERFORCE change 96007 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Apr 2006 15:12:59 -0000 On Monday 24 April 2006 18:04, John Birrell wrote: > On Mon, Apr 24, 2006 at 05:48:58PM -0400, John Baldwin wrote: > > 1) I've already completely redone all of the locking in the > > kernel linker to use a big sx lock around the whole kernel > > linker. I have to tidy up some issues with ndis still. > > > > 2) Tell me what dtrace is trying to do and let's see if we > > can provide an API hook in the kernel linker for it instead > > of having DTrace grovel around in the linker's internals. > > Then DTrace doesn't need to be aware of any locking for the > > kernel linker. > > What I would like to do is have DTrace call a kern_linker > function specifying a callback function that the linker > would call for each module. The function needs to pass back > an opaque argument, plus a pointer to the linker file structure. > > DTrace wants the module info not to change while it looks at > the contents of the linker file structure. DTrace doesn't > need to know how the modules are listed or locked, but it > definitely needs to be able to allocate memory with wait > while it is looking at the module data. Great, that's pretty much what I need to do for ndis as well. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org