On Fri, 30 May 2008 15:36:14 -0700 Tim Bird <tim.bird@xxxxxxxxxxx> wrote: > Josh Boyer wrote: > > lttng can trace quite a few events. Interrupts, system calls, etc. > > Might be worth a look, and it's quite well maintained against various > > kernel versions. > > It's pretty heavyweight, but you could use filters to cut down on > the events traced. By default output goes to the file system, which > could be on pramfs. (Or NFS - I'm sorry I lost track of the original > request - don't know if this is an option or not.) Indeed, it is fairly heavy in what it traces. I was just suggesting it as a starting point. > I'm not sure, however, that the buffers are pushed to user-space, > through the daemon, and back to the file system in an expedient manner. > I agree it might be worth a look for this use case. We use it at > Sony quite a bit and it's valuable. With a little bit of work, you could have it trace into a circular buffer in DRAM. Then you can preserve that via mem= reservations, etc. josh -- To unsubscribe from this list: send the line "unsubscribe linux-embedded" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
