I missed your original post. If you want some form or generic tracing in the kernel then DProbes with LTT might help. With these tools you can build tracepoints without modifying the source. You could use system.map to generate simple tracepoint definitions (having written yourself a small program to parse the map output). Richard Richard Moore - RAS Project Lead - Linux Technology Centre (ATS-PIC). http://oss.software.ibm.com/developerworks/opensource/linux Office: (+44) (0)1962-817072, Mobile: (+44) (0)7768-298183 IBM UK Ltd, MP135 Galileo Centre, Hursley Park, Winchester, SO21 2JN, UK Constantin Loizides <[EMAIL PROTECTED]> on 05/07/2001 16:38:26 Please respond to Constantin Loizides <[EMAIL PROTECTED]> To: Tom spaziani <[EMAIL PROTECTED]> cc: linux-kernel <[EMAIL PROTECTED]> Subject: Re: Kernel Module tracing. > I want this. I've been thinking about it since your original post, and I also would be very much interested in having such a great tool by hand. Please mail me any information, or code to try, thanx! > > Perhaps you should also think about a non-devfs way of doing this, I don't > know, it's a matter of taste. Here's a Rube Goldbergesque way: when the > client registers, export a dynamically allocated major number through proc > and let the user mknod a device with that major. Yes I think, that would be a great alternative, using good old /proc. Constantin - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
