On 31 January 2013 14:36, Fabio Baltieri <fabio.baltieri@xxxxxxxxxx> wrote: > Current code uses ->cpu to track policy->cpu and get the timestamp, I > can modify it to point to the current cpu and use it in timer_init *and* > add a new field just to track leader_cpu but I don't see the benefits. > Am I missing something? Current code doesn't use cdbs->cpu for any cpu leaving the leader. So, we can use that field to keep local cpus. And for any cpu we can get the updated leader cpu with following: j_cdbs->cur_policy->cpu :) -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
