summaryrefslogtreecommitdiffstats
path: root/tools
diff options
context:
space:
mode:
authorPeter Zijlstra <a.p.zijlstra@chello.nl>2009-12-16 17:55:54 +0100
committerIngo Molnar <mingo@elte.hu>2009-12-16 18:30:11 +0100
commitf4c4176f21533e22bcc292030da72bcfa105f5b8 (patch)
tree9e4376f5ff4dc3fb0f333faca94f219570df9af8 /tools
parent9b33827de63539c7c3314ddf890fb216e4acf3d8 (diff)
downloadop-kernel-dev-f4c4176f21533e22bcc292030da72bcfa105f5b8.zip
op-kernel-dev-f4c4176f21533e22bcc292030da72bcfa105f5b8.tar.gz
perf events: Allow per-task-per-cpu counters
In order to allow for per-task-per-cpu counters, useful for scalability when profiling task hierarchies, we allow installing events with event->cpu != -1 in task contexts. __perf_event_sched_in() already skips events where ->cpu mis-matches the current cpu, fix up __perf_install_in_context() and __perf_event_enable() to also respect this filter. This does lead to vary hard to interpret enabled/running times for such counters, but I don't see a simple solution for that. Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl> Cc: Arnaldo Carvalho de Melo <acme@redhat.com> Cc: fweisbec@gmail.com Cc: Paul Mackerras <paulus@samba.org> LKML-Reference: <20091216165904.831451147@chello.nl> Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud