diff options
author | Anton Blanchard <anton@samba.org> | 2011-07-04 13:57:50 +0200 |
---|---|---|
committer | Ingo Molnar <mingo@elte.hu> | 2011-07-05 10:44:44 +0200 |
commit | 5d67be97f8903d05ce53597fb5f3bc25a45e8026 (patch) | |
tree | 5ce8c2407d50570d7fee79b9c7f24e8eb89384b4 /crypto | |
parent | Merge branch 'core' of git://git.kernel.org/pub/scm/linux/kernel/git/rric/opr... (diff) | |
download | linux-5d67be97f8903d05ce53597fb5f3bc25a45e8026.tar.xz linux-5d67be97f8903d05ce53597fb5f3bc25a45e8026.zip |
perf report/annotate/script: Add option to specify a CPU range
Add an option to perf report/annotate/script to specify which
CPUs to operate on. This enables us to take a single system wide
profile and analyse each CPU (or group of CPUs) in isolation.
This was useful when profiling a multiprocess workload where the
bottleneck was on one CPU but this was hidden in the overall
profile. Per process and per thread breakdowns didn't help
because multiple processes were running on each CPU and no
single process consumed an entire CPU.
The patch converts the list of CPUs returned by cpu_map__new
into a bitmap for fast lookup. I wanted to use -C to be
consistent with perf top/record/stat, but unfortunately perf
report already uses -C <comms>.
v2: Incorporate suggestions from David Ahern:
- Added -c to perf script
- Check that SAMPLE_CPU is set when -c is used
- Update documentation
v3: Create perf_session__cpu_bitmap()
Signed-off-by: Anton Blanchard <anton@samba.org>
Acked-by: David Ahern <dsahern@gmail.com>
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Paul Mackerras <paulus@samba.org>
Link: http://lkml.kernel.org/r/20110704215750.11647eb9@kryten
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions