Re: [PATCH v7] Cpufreq: Fix governor start/stop race condition
From: Viresh Kumar
Date: Wed Jun 19 2013 - 02:18:07 EST
On 19 June 2013 10:54, Xiaoguang Chen <chenxg@xxxxxxxxxxx> wrote:
> Cpufreq governor's stop and start operation should be kept in sequence.
> If not, there will be unexpected behavior, for example:
> There are 4 CPUs and policy->cpu=CPU0, CPU1/2/3 are linked to CPU0.
> The normal sequence is as below:
> 1) Current governor is userspace, One application tries to set
> governor to ondemand. It will call __cpufreq_set_policy in which it
> will stop userspace governor and then start ondemand governor.
> 2) Current governor is userspace, Now CPU0 hotplugs in CPU3(put CPU3 online),
You need a space before (
Otherwise looks good. Add my
Acked-by: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
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/