Loop block overhead

Loop block overhead

[lhmaster2 .]

Dear all,

Is there any way to make perf report retrieve the total overhead due
to loop blocks, like what is done with total function overhead?

Lucas

Re: Loop block overhead

[Andi Kleen]

"lhmaster2 ." <lhmaster2@gmail.com> writes:

> Dear all,
>
> Is there any way to make perf report retrieve the total overhead due
> to loop blocks, like what is done with total function overhead?

perf has no idea what a loop is unfortunately.

You can use srcline as a sort key to account per line.

-Andi

-- 
ak@linux.intel.com -- Speaking for myself only

Re: Loop block overhead

[lhmaster2 .]

Thank you for the info.

I researched a bit and found that srcline uses addr2line capabilities
to map memory addressed into source lines. Nevertheless, as I invoke

$ perf report -s srcline, sys

only the original mem addresses are printed. Should I pass some
special parameter for perf record to make it work?

Best regards,
Lucas


On 30 April 2014 17:10, Andi Kleen <andi@firstfloor.org> wrote:
>
> "lhmaster2 ." <lhmaster2@gmail.com> writes:
>
> > Dear all,
> >
> > Is there any way to make perf report retrieve the total overhead due
> > to loop blocks, like what is done with total function overhead?
>
> perf has no idea what a loop is unfortunately.
>
> You can use srcline as a sort key to account per line.
>
> -Andi
>
> --
> ak@linux.intel.com -- Speaking for myself only

Re: Loop block overhead

[Namhyung Kim]

Hi lhmaster,

On Wed, 7 May 2014 14:55:05 -0300, lhmaster wrote:
> Thank you for the info.
>
> I researched a bit and found that srcline uses addr2line capabilities
> to map memory addressed into source lines. Nevertheless, as I invoke
>
> $ perf report -s srcline, sys
>
> only the original mem addresses are printed. Should I pass some
> special parameter for perf record to make it work?

Nope.  But you need to make sure that your binary was built with
debuginfo and the binutils is available on your system.

Thanks,
Namhyung