Re: [ANNOUNCE] oprofile profiler

[Karim Yaghmour]

Hello John,

This is really interesting. Great stuff.

As Alan had once suggested, it would be very interesting to have this
information correlated with the content of the traces collected using
the Linux Trace Toolkit (www.opersys.com/LTT). For instance, you could see
how many cache faults the read() or write() operation of your application
generated and other unique info. It would also be possible to enhance
the post-mortem analysis done by LTT to take in account this data.
You could also use LTT's dynamic event creation mechanism to log the
profiling data as part of the trace.

There are definitely opportunities for interfacing/integrating here.

Let me know what you think.

Best regards

Karim

John Levon wrote:
> 
> oprofile is a low-overhead statistical profiler capable of
> instruction-grain profiling of the kernel (including interrupt handlers),
> modules, and user-space libraries and binaries.
> 
> It uses the Intel P6 performance counters as a source of interrupts to
> trigger the accounting handler in a manner similar to that of Digital's
> DCPI. All running processes, and the kernel, are profiled by default. The
> profiles can be extracted at any time with a simple utility. The system
> consists of a kernel module and a simple background daemon.
> 
> Typical overhead is around 3 or 4 percent. Worst case overhead on a
> Pentium II 350 UP system is around 10-15%
> 
> You can read a little more about oprofile, and download a very alpha
> version at :
> 
> http://oprofile.sourceforge.net/
> 
> oprofile is released under the GNU GPL.
> 
> thanks
> john
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [e-mail]
> Please read the FAQ at http://www.tux.org/lkml/

-- 
===================================================
                 Karim Yaghmour
               [e-mail]
          Operating System Consultant
 (Linux kernel, real-time and distributed systems)
===================================================