Re: [PATCH v7 2/4] cpufreq: ondemand: call dbs_check_cpu only when necessary
From: Viresh Kumar
Date: Thu Jan 31 2013 - 03:42:40 EST
On 31 January 2013 14:09, Fabio Baltieri <fabio.baltieri@xxxxxxxxxx> wrote:
> Ok, now I see the problem: cdbs->cpu is initialized only on the leader
> cpu and this is working by coincidence on my system, while
> cdbs->time_stamp is initialized only on the leader cpu, and that should
> be correct even when cpu hotplugging as that's reinitialized every time.
>
> That's a fix so I'll send a patch just to set ->cpu into the
> for_each_cpu cycle.
That's not enough. You need to set ->cpu to j and not policy->cpu as we
discussed it earlier (params to timer init and exit.).
And so, we need to get policy->cpu somehow and get its timestamp.
--
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/