Date: Tue, 25 Apr 2006 10:59:35 -0400 From: John Baldwin <jhb@freebsd.org> To: John Birrell <jb@what-creek.com> Cc: Perforce Change Reviews <perforce@freebsd.org> Subject: Re: PERFORCE change 96007 for review Message-ID: <200604251059.36556.jhb@freebsd.org> In-Reply-To: <20060424220405.GA62694@what-creek.com> References: <200604241913.k3OJDEAq055317@repoman.freebsd.org> <200604241748.59461.jhb@freebsd.org> <20060424220405.GA62694@what-creek.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200604251059.36556.jhb>