Re: [PATCH v5 4/9] perf report: Add callchain value option

From: Namhyung Kim
Date: Thu Nov 19 2015 - 20:39:55 EST


On Thu, Nov 19, 2015 at 10:59:14AM -0300, Arnaldo Carvalho de Melo wrote:
> Em Mon, Nov 09, 2015 at 02:45:41PM +0900, Namhyung Kim escreveu:
> > Now -g/--call-graph option supports how to display callchain values.
> > Possible values are 'percent', 'period' and 'count'. The percent is
> > same as before and it's the default behavior. The period displays the
> > raw period value rather than the percentage. The count displays the
> > number of occurrences.
> >
> > $ perf report --no-children --stdio -g percent
> > ...
> > 39.93% swapper [kernel.vmlinux] [k] intel_idel
> > |
> > ---intel_idle
> > cpuidle_enter_state
> > cpuidle_enter
> > call_cpuidle
> > cpu_startup_entry
> > |
> > |--28.63%-- start_secondary
> > |
> > --11.30%-- rest_init
>
> So, if I try to do:
>
> perf report --no-children --stdio -g percent,count
>
> It shows just 'count', i.e. the last of these options, is this an
> intended limitation?
>
> I'm applying it as-is, but I can see no reason why we wouldn't want to
> lift this limitation.


Hmm.. I expected just one value type is used, but yes, we might want
to support to print multiple values if needed.

Thanks,
Namhyung


>
> > $ perf report --no-children --show-total-period --stdio -g period
> > ...
> > 39.93% 13018705 swapper [kernel.vmlinux] [k] intel_idel
> > |
> > ---intel_idle
> > cpuidle_enter_state
> > cpuidle_enter
> > call_cpuidle
> > cpu_startup_entry
> > |
> > |--9334403-- start_secondary
> > |
> > --3684302-- rest_init
> >
> > $ perf report --no-children --show-nr-samples --stdio -g count
> > ...
> > 39.93% 80 swapper [kernel.vmlinux] [k] intel_idel
> > |
> > ---intel_idle
> > cpuidle_enter_state
> > cpuidle_enter
> > call_cpuidle
> > cpu_startup_entry
> > |
> > |--57-- start_secondary
> > |
> > --23-- rest_init
> >
> > Acked-by: Brendan Gregg <brendan.d.gregg@xxxxxxxxx>
> > Signed-off-by: Namhyung Kim <namhyung@xxxxxxxxxx>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/