Venkatesh Pallipadi 4ec223d02f [CPUFREQ] Fix ondemand vs suspend deadlock
Rootcaused the bug to a deadlock in cpufreq and ondemand. Due to non-existent
ordering between cpu_hotplug lock and dbs_mutex. Basically a race condition
between cpu_down() and do_dbs_timer().

cpu_down() flow:
* cpu_down() call for CPU 1
* Takes hot plug lock
* Calls pre down notifier
*     cpufreq notifier handler calls cpufreq_driver_target() which takes
      cpu_hotplug lock again. OK as cpu_hotplug lock is recursive in same
      process context
* CPU 1 goes down
* Calls post down notifier
*     cpufreq notifier handler calls ondemand event stop which takes dbs_mutex

So, cpu_hotplug lock is taken before dbs_mutex in this flow.

do_dbs_timer is triggerred by a periodic timer event.
It first takes dbs_mutex and then takes cpu_hotplug lock in
cpufreq_driver_target().
Note the reverse order here compared to above. So, if this timer event happens
at right moment during cpu_down, system will deadlok.

Attached patch fixes the issue for both ondemand and conservative.

Signed-off-by: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
Signed-off-by: Dave Jones <davej@redhat.com>
2006-06-21 18:30:26 -04:00
..
2006-06-17 21:30:16 -07:00
2006-06-17 10:44:26 -07:00
2006-06-17 21:25:58 -07:00
2006-05-03 20:05:41 -07:00
2006-05-21 12:59:18 -07:00
2006-06-17 21:30:14 -07:00
2006-06-13 20:29:04 -04:00
2006-06-05 12:29:17 -07:00
2006-06-08 15:24:46 -04:00
2006-06-19 18:01:27 -07:00
2006-05-03 20:05:41 -07:00
2006-06-13 20:29:04 -04:00
2006-06-17 21:18:43 -07:00
2006-06-17 21:18:43 -07:00