[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <55788592.8010701@gmail.com>
Date: Wed, 10 Jun 2015 12:44:34 -0600
From: David Ahern <dsahern@...il.com>
To: Jiri Olsa <jolsa@...nel.org>,
Arnaldo Carvalho de Melo <acme@...nel.org>
CC: lkml <linux-kernel@...r.kernel.org>,
Adrian Hunter <adrian.hunter@...el.com>,
Andi Kleen <ak@...ux.intel.com>,
Ingo Molnar <mingo@...nel.org>,
Namhyung Kim <namhyung@...nel.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Stephane Eranian <eranian@...gle.com>
Subject: Re: [PATCH 25/25] perf stat: Introduce --per-task option
On 6/10/15 12:10 PM, Jiri Olsa wrote:
> Currently all the -p option PID arguments tasks values
> get aggregated and printed as single values.
>
> Adding --per-tasks option to print values per task.
>
> $ perf stat -e cycles,instructions --per-task -p 12451,16173
> ^C
> Performance counter stats for process id '12451,16173':
>
> TASK-12451 77,784 cycles
> TASK-16173 64,809 cycles
> TASK-12451 14,432 instructions
> TASK-16173 14,452 instructions
>
> 3.854957122 seconds time elapsed
>
> Also woks under interval mode:
>
> $ ./perf stat -e cycles,instructions --per-task -p 16431,16173 -I 1000
> # time task counts unit events
> 1.000085816 TASK-16173 0 cycles
> 1.000085816 TASK-16431 3,358,360,926 cycles
> 1.000085816 TASK-16173 0 instructions
> 1.000085816 TASK-16431 9,062,422,086 instructions
> 2.000212262 TASK-16173 65,386 cycles
> 2.000212262 TASK-16431 3,349,355,309 cycles
> 2.000212262 TASK-16173 12,151 instructions
> 2.000212262 TASK-16431 9,039,401,422 instructions
> 3.000333402 TASK-16173 62,797 cycles
> 3.000333402 TASK-16431 3,357,140,183 cycles
> 3.000333402 TASK-16173 12,208 instructions
> 3.000333402 TASK-16431 9,058,080,762 instructions
> ^C 3.375949851 TASK-16173 0 cycles
> 3.375949851 TASK-16431 1,264,764,804 cycles
> 3.375949851 TASK-16173 0 instructions
> 3.375949851 TASK-16431 3,414,532,317 instructions
>
Why not print $comm-$pid versus TASK-$pid?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists