diff options
author | Stephane Eranian <eranian@google.com> | 2010-02-08 18:06:01 +0300 |
---|---|---|
committer | Ingo Molnar <mingo@elte.hu> | 2010-02-26 12:56:53 +0300 |
commit | d76a0812ac4139ceb54daab3cc70e1bd8bd9d43a (patch) | |
tree | 81413e2271b310a698bec191a8f0ded5cdcfa2de /mm | |
parent | 3a0304e90aa5a2c0c308a05d28f7d109a48d8539 (diff) | |
download | linux-d76a0812ac4139ceb54daab3cc70e1bd8bd9d43a.tar.xz |
perf_events: Add new start/stop PMU callbacks
In certain situations, the kernel may need to stop and start the same
event rapidly. The current PMU callbacks do not distinguish between stop
and release (i.e., stop + free the resource). Thus, a counter may be
released, then it will be immediately re-acquired. Event scheduling will
again take place with no guarantee to assign the same counter. On some
processors, this may event yield to failure to assign the event back due
to competion between cores.
This patch is adding a new pair of callback to stop and restart a counter
without actually release the underlying counter resource. On stop, the
counter is stopped, its values saved and that's it. On start, the value
is reloaded and counter is restarted (on x86, actual restart is delayed
until perf_enable()).
Signed-off-by: Stephane Eranian <eranian@google.com>
[ added fallback to ->enable/->disable for all other PMUs
fixed x86_pmu_start() to call x86_pmu.enable()
merged __x86_pmu_disable into x86_pmu_stop() ]
Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
LKML-Reference: <4b703875.0a04d00a.7896.ffffb824@mx.google.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'mm')
0 files changed, 0 insertions, 0 deletions