Re: Profiling a program's runtime

[Frederic Weisbecker <fweisbec@gmail.com>]

On Fri, Feb 04, 2011 at 06:41:57PM +0100, Christoph Bartoschek wrote:
> Frederic Weisbecker wrote:
> 
> > 
> > If I understood you well, you make a difference between:
> > 
> > - profiling only the code executed by your task
> > - profiling any code executed while your task was existing,
> > which includes what happens on other CPUs and other tasks that
> > may share the same CPU? Everything in fact?
> > 
> > So for the case, you just launch:
> > 
> > perf record -g my_task
> > 
> > For the second case, use -a for system wide profiling while
> > your task exists:
> > 
> > ./perf record -a -g my_task
> 
> I am not interessted in code that is executed in other processes while my 
> task exists. 
> 
> I want that not only the CPU time is counted that my task uses, but also the 
> time my task waits.

The time your task waits, other tasks executes :-/  (including idle in the scheme)
 
> For example, if my task waits for network packets in a read() then the time  
> should be added to the read() function. Other profilers I know would not 
> count the time when the process is blocked.

What do you mean by adding time to read?

I'm very confused with what you want.