Re: [PATCH V2 7/7] cpufreq: Remove cpufreq_governor_lock

2016-02-03 Thread Viresh Kumar
On 03-02-16, 19:32, Viresh Kumar wrote: > We used to drop policy->rwsem just before calling __cpufreq_governor() > in some cases earlier and so it was possible that __cpufreq_governor() > runs concurrently via separate threads. > > In order to guarantee valid state transitions for governors, > 'go

[PATCH V2 7/7] cpufreq: Remove cpufreq_governor_lock

2016-02-03 Thread Viresh Kumar
We used to drop policy->rwsem just before calling __cpufreq_governor() in some cases earlier and so it was possible that __cpufreq_governor() runs concurrently via separate threads. In order to guarantee valid state transitions for governors, 'governor_enabled' was required to be protected using s