aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/net_dropmonitor.py
diff options
context:
space:
mode:
authorSrivatsa S. Bhat <[email protected]>2014-03-11 02:11:11 +0530
committerRafael J. Wysocki <[email protected]>2014-03-20 13:43:47 +0100
commit3289705fe2b429569f37730ecf660719b8924420 (patch)
treeb4021a25d0da5fdebd2d87c81c5a0b1df10fb022 /tools/perf/scripts/python/net_dropmonitor.py
parentcf0485a2ac70acb1bc83f6310a7ebef3070f0333 (diff)
hwmon, coretemp: Fix CPU hotplug callback registration
Subsystems that want to register CPU hotplug callbacks, as well as perform initialization for the CPUs that are already online, often do it as shown below: get_online_cpus(); for_each_online_cpu(cpu) init_cpu(cpu); register_cpu_notifier(&foobar_cpu_notifier); put_online_cpus(); This is wrong, since it is prone to ABBA deadlocks involving the cpu_add_remove_lock and the cpu_hotplug.lock (when running concurrently with CPU hotplug operations). Instead, the correct and race-free way of performing the callback registration is: cpu_notifier_register_begin(); for_each_online_cpu(cpu) init_cpu(cpu); /* Note the use of the double underscored version of the API */ __register_cpu_notifier(&foobar_cpu_notifier); cpu_notifier_register_done(); Fix the hwmon coretemp code by using this latter form of callback registration. Cc: Fenghua Yu <[email protected]> Cc: Jean Delvare <[email protected]> Cc: Ingo Molnar <[email protected]> Acked-by: Guenter Roeck <[email protected]> Signed-off-by: Srivatsa S. Bhat <[email protected]> Signed-off-by: Rafael J. Wysocki <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/net_dropmonitor.py')
0 files changed, 0 insertions, 0 deletions