Re: [PATCH v3 1/4] perf report: Support folded callchain mode on --stdio

From: Jiri Olsa
Date: Tue Nov 03 2015 - 03:22:01 EST


On Tue, Nov 03, 2015 at 04:18:28PM +0900, Namhyung Kim wrote:
> Add new call chain option (-g) 'folded' to print callchains in a line.
> The callchains are separated by semicolons, and preceded by (absolute)
> percent values and a space.
>
> For example, following 20 lines can be printed in 3 lines with the
> folded output mode;
>
> $ perf report -g flat --no-children | grep -v ^# | head -20
> 60.48% swapper [kernel.vmlinux] [k] intel_idle
> 54.60%
> intel_idle
> cpuidle_enter_state
> cpuidle_enter
> call_cpuidle
> cpu_startup_entry
> start_secondary
>
> 5.88%
> intel_idle
> cpuidle_enter_state
> cpuidle_enter
> call_cpuidle
> cpu_startup_entry
> rest_init
> start_kernel
> x86_64_start_reservations
> x86_64_start_kernel
>
> $ perf report -g folded --no-children | grep -v ^# | head -3
> 60.48% swapper [kernel.vmlinux] [k] intel_idle
> 54.60% intel_idle;cpuidle_enter_state;cpuidle_enter;call_cpuidle;cpu_startup_entry;start_secondary
> 5.88% intel_idle;cpuidle_enter_state;cpuidle_enter;call_cpuidle;cpu_startup_entry;rest_init;start_kernel;x86_64_start_reservations;x86_64_start_kernel
>
> This mode is supported only for --stdio now and intended to be used by
> some scripts like in FlameGraphs[1]. Support for other UI might be
> added later.
>
> [1] http://www.brendangregg.com/FlameGraphs/cpuflamegraphs.html
>
> Requested-by: Brendan Gregg <brendan.d.gregg@xxxxxxxxx>
> Signed-off-by: Namhyung Kim <namhyung@xxxxxxxxxx>
> ---
> tools/perf/ui/stdio/hist.c | 54 +++++++++++++++++++++++++++++++++++++++++++++
> tools/perf/util/callchain.c | 6 +++++
> tools/perf/util/callchain.h | 3 ++-
> 3 files changed, 62 insertions(+), 1 deletion(-)

missing doc update, otherwise

Acked-by: Jiri Olsa <jolsa@xxxxxxxxxx>

thanks,
jirka
--
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/