Re: [PATCH] perf: add callgrind conversion tool

2013-03-26 Thread Roberto Vitillo
>> LIB_OBJS += $(OUTPUT)ui/setup.o >> LIB_OBJS += $(OUTPUT)ui/helpline.o >> @@ -528,6 +532,7 @@ BUILTIN_OBJS += $(OUTPUT)builtin-kmem.o >> BUILTIN_OBJS += $(OUTPUT)builtin-lock.o >> BUILTIN_OBJS += $(OUTPUT)builtin-kvm.o >> BUILTIN_OBJS += $(OUTPUT)builtin-inject.o >> +BUILTIN_OBJS += $(OUTPUT

Re: [PATCH] perf: add callgrind conversion tool

2013-03-03 Thread Namhyung Kim
Hi Roberto, On Wed, 27 Feb 2013 00:26:33 +0100, Roberto Vitillo wrote: > The proposed patch adds the convert tool to perf which allows to convert a > perf.data file to a callgrind data file which can subsequently be displayed > with kcachegrind. Callgraphs are not supported. I was thinking about

Re: [PATCH] perf: add callgrind conversion tool

2013-02-28 Thread Namhyung Kim
Hi Roberto, On Wed, 27 Feb 2013 00:26:33 +0100, Roberto Vitillo wrote: > The proposed patch adds the convert tool to perf which allows to convert a > perf.data file to a callgrind data file which can subsequently be displayed > with kcachegrind. Callgraphs are not supported. > > In order to speed

Re: [PATCH] perf: add callgrind conversion tool

2013-02-27 Thread Ingo Molnar
* Roberto Vitillo wrote: > The proposed patch adds the convert tool to perf which allows to convert a > perf.data file to a callgrind data file which can subsequently be displayed > with > kcachegrind. Callgraphs are not supported. Would be nice to add a usecase description to the documentat

[PATCH] perf: add callgrind conversion tool

2013-02-26 Thread Roberto Vitillo
The proposed patch adds the convert tool to perf which allows to convert a perf.data file to a callgrind data file which can subsequently be displayed with kcachegrind. Callgraphs are not supported. In order to speed up the converter I am not piping to addr2line, this means that the code depends o