diff options
author | Peter Zijlstra <a.p.zijlstra@chello.nl> | 2009-03-13 12:21:30 +0100 |
---|---|---|
committer | Ingo Molnar <mingo@elte.hu> | 2009-04-06 09:29:32 +0200 |
commit | 60b3df9c1e24a18aabb412da9905208c5f04ebea (patch) | |
tree | 2c132d1a82648b176f8662cea32f51c208517dd5 /kernel | |
parent | 755642322aa66fbc5421a35fd3e1733f73e20083 (diff) | |
download | linux-60b3df9c1e24a18aabb412da9905208c5f04ebea.tar.gz linux-60b3df9c1e24a18aabb412da9905208c5f04ebea.tar.bz2 linux-60b3df9c1e24a18aabb412da9905208c5f04ebea.zip |
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 'kernel')
0 files changed, 0 insertions, 0 deletions