Re: [PATCH V2 6/9] cpufreq: ondemand: queue work for policy->cpus together
From: Viresh Kumar
Date: Mon Sep 07 2015 - 22:11:13 EST
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.
--
viresh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/