perf_counter: don't count scheduler ticks as context switches
authorPaul Mackerras <paulus@samba.org>
Mon, 11 May 2009 05:46:10 +0000 (15:46 +1000)
committerIngo Molnar <mingo@elte.hu>
Mon, 11 May 2009 10:10:53 +0000 (12:10 +0200)
commita08b159fc243dbfe415250466d24cfc5010deee5
tree39bb59aaf183021e6d9b02ed26dc8a4930d00f0b
parent6751b71ea2c7ab8c0d65f01973a3fc8ea16992f4
perf_counter: don't count scheduler ticks as context switches

The context-switch software counter gives inflated values at present
because each scheduler tick and each process-wide counter
enable/disable prctl gets counted as a context switch.

This happens because perf_counter_task_tick, perf_counter_task_disable
and perf_counter_task_enable all call perf_counter_task_sched_out,
which calls perf_swcounter_event to record a context switch event.

This fixes it by introducing a variant of perf_counter_task_sched_out
with two underscores in front for internal use within the perf_counter
code, and makes perf_counter_task_{tick,disable,enable} call it.  This
variant doesn't record a context switch event, and takes a struct
perf_counter_context *.  This adds the new variant rather than
changing the behaviour or interface of perf_counter_task_sched_out
because that is called from other code.

[ Impact: fix inflated context-switch event counts ]

Signed-off-by: Paul Mackerras <paulus@samba.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Corey Ashford <cjashfor@linux.vnet.ibm.com>
LKML-Reference: <18951.48034.485580.498953@drongo.ozlabs.ibm.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
kernel/perf_counter.c