On 08-09-15, 03:33, Rafael J. Wysocki wrote:
/* Make sure the work is not canceled on policy->cpus */
I'm not sure what scenario can lead to that. Care to explain?
CPUFREQ_GOV_STOP event called for the policy and so all its works are in canceled state.
if (!dbs_info->cdbs.shared->policy) continue;
next_sampling = jiffies + usecs_to_jiffies(new_rate); appointed_at = dbs_info->cdbs.dwork.timer.expires;
For that to work we always need to do stuff for policy->cpus in sync. Do we?
Hmm, we are not in 100% sync for sure. Will check that again.