RE: [Fault-injection-developer] Couple of issues downloading and building the FITH source code

[Rob R. <err...@li...>]

On Tue, 2002-10-22 at 11:22, Lynch, Rusty wrote:
> I think we need to be a little more clear on the terms we are using.  I
> think that when Rob refers to "extending dprobes", he means patching dprobes
> to enable some additional features, not taking advantage of various kernel
> hooks that the dprobes patch adds to the kernel.
> 
> For example, a very small tweak to dprobes could enable an extra instruction
> in the probe rpn files that allows arbitrary exit points to be called from
> the rpn file.  This could enable something like:
> 1. Some user space tool analysis a driver module and then and generates a
> rpn file that would insert probe points for each of the in/out operations
> where each probe point calls an exit function in a FITH loadable kernel
> module
> 2. Once the exit function in the FITH module has been called then the rest
> of the design for FITH would be the same
> 
> 	-rusty 
> 

Yes, that was similar to what I was thinking. It would be nice though,
if the user-space tool could also work on more than just modules though.
Does dprobes allow you to insert anywhere in the kernel (i.e. not just
kernel modules)? It would be nice to be able to insert probe points for
compiled in drivers as well. This could be tricky, but you could use the
tool to run through the kernel System.map and vmlinux (uncompressed
compiled kernel ELF file) to figure out where to insert probe points in
the rpn file for a running kernel. Just a thought...

-- 
Rob Rhoads                     mailto:err...@li...
Telecom Software Platforms     office: 503-677-5498
Intel Communications Group

<disclaimer value="pointless">
This email message solely contains my own personal views, 
and not necessarily those of my employer.
</disclaimer>