diff options
author | Peter Zijlstra <a.p.zijlstra@chello.nl> | 2009-03-13 07:21:30 -0400 |
---|---|---|
committer | Ingo Molnar <mingo@elte.hu> | 2009-04-06 03:29:32 -0400 |
commit | 60b3df9c1e24a18aabb412da9905208c5f04ebea (patch) | |
tree | 2c132d1a82648b176f8662cea32f51c208517dd5 /arch | |
parent | 755642322aa66fbc5421a35fd3e1733f73e20083 (diff) |
perf_counter: add comment to barrier
We need to ensure the enabled=0 write happens before we
start disabling the actual counters, so that a pcm_amd_enable()
will not enable one underneath us.
I think the race is impossible anyway, we always balance the
ops within any one context and perform enable() with IRQs disabled.
Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'arch')
-rw-r--r-- | arch/x86/kernel/cpu/perf_counter.c | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/arch/x86/kernel/cpu/perf_counter.c b/arch/x86/kernel/cpu/perf_counter.c index 1cedc3468ce5..a2e3b76bfdc1 100644 --- a/arch/x86/kernel/cpu/perf_counter.c +++ b/arch/x86/kernel/cpu/perf_counter.c | |||
@@ -247,6 +247,10 @@ static u64 pmc_amd_save_disable_all(void) | |||
247 | 247 | ||
248 | enabled = cpuc->enabled; | 248 | enabled = cpuc->enabled; |
249 | cpuc->enabled = 0; | 249 | cpuc->enabled = 0; |
250 | /* | ||
251 | * ensure we write the disable before we start disabling the | ||
252 | * counters proper, so that pcm_amd_enable() does the right thing. | ||
253 | */ | ||
250 | barrier(); | 254 | barrier(); |
251 | 255 | ||
252 | for (idx = 0; idx < nr_counters_generic; idx++) { | 256 | for (idx = 0; idx < nr_counters_generic; idx++) { |