> hm, I'm getting following stats when running perf stat in similar scenario:
>
> [jolsa@dhcp-26-214 perf]$ ./perf stat -e
> '{task-clock,cpu-clock,instructions}' kill
> usage: kill [ -s signal | -p ] [ -a ] pid ...
> kill -l [ signal ]
>
> Performance counter stats for 'kill':
>
> 1.039561 task-clock # 0.479 CPUs utilized
> <not counted> cpu-clock
> 2,281,726 instructions # 0.00 insns per cycle
>
> 0.002168502 seconds time elapsed
> ...
>
> seems wrong ;-) will check
>
> thanks,
> jirka
creating groups with perf stat is new for me and not documented ?
running the same works for me:
[capjo@e6410 ~]$ perf stat -v -e '{task-clock,cpu-clock,instructions}' kill
usage: kill [ -s signal | -p ] [ -a ] pid ...
kill -l [ signal ]
task-clock: 884808 884808 884808
cpu-clock: 885924 884808 884808
instructions: 735287 884808 884808
Performance counter stats for 'kill':
0.884808 task-clock # 0.687 CPUs utilized
0.885924 cpu-clock
735,287 instructions # 0.00 insns per cycle
0.001287584 seconds time elapsed
[capjo@e6410 ~]$ perf --version
perf version 3.7-5
[capjo@e6410 ~]$ uname -a
Linux e6410 3.7.4-1-ARCH #1 SMP PREEMPT Mon Jan 21 23:05:29 CET 2013
x86_64 GNU/Linux
--
To unsubscribe from this list: send the line "unsubscribe linux-perf-users" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
