Re: [PATCH 12/12] cpufreq: governor: Narrow down the dbs_data_mutex coverage

2016-02-18 Thread Rafael J. Wysocki
On Thu, Feb 18, 2016 at 7:20 AM, Viresh Kumar wrote: > On 18-02-16, 02:38, Rafael J. Wysocki wrote: >> From: Rafael J. Wysocki >> >> Since cpufreq_governor_dbs() is now always called with policy->rwsem >> held, it cannot be executed twice in parallel for the same policy. >> Thus it is not necessa

Re: [PATCH 12/12] cpufreq: governor: Narrow down the dbs_data_mutex coverage

2016-02-17 Thread Viresh Kumar
On 18-02-16, 02:38, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > Since cpufreq_governor_dbs() is now always called with policy->rwsem > held, it cannot be executed twice in parallel for the same policy. > Thus it is not necessary to hold dbs_data_mutex around the invocations > of cpufre

[PATCH 12/12] cpufreq: governor: Narrow down the dbs_data_mutex coverage

2016-02-17 Thread Rafael J. Wysocki
From: Rafael J. Wysocki Since cpufreq_governor_dbs() is now always called with policy->rwsem held, it cannot be executed twice in parallel for the same policy. Thus it is not necessary to hold dbs_data_mutex around the invocations of cpufreq_governor_start/stop/limits() from it as those functions