From 2b65c55c0dd7e370529963093ef890ae7bc0badd Mon Sep 17 00:00:00 2001 From: Mike Turquette Date: Mon, 7 Mar 2011 15:40:23 -0600 Subject: cpufreq: hotplug: don't synch threads on jiffies cpufreq-hotplug was always designed to run as a single thread that takes aggregate load of all CPUs into account. As such there is no need to synchronize multiple threads to execute at the same time. This sychronization mechanism also causes execution of the do_dbs_check function to be somewhat erratically scheduled. Removing it causes scheduling of this function to reliably happen based soley on the supplied sampling_rate parameter. Change-Id: If0edc89996f0d5763502236b225835dd9f4ab3c9 Signed-off-by: Mike Turquette --- drivers/cpufreq/cpufreq_hotplug.c | 1 - 1 file changed, 1 deletion(-) (limited to 'drivers/cpufreq') diff --git a/drivers/cpufreq/cpufreq_hotplug.c b/drivers/cpufreq/cpufreq_hotplug.c index 79634e07ddc5..dac7b9bf7b80 100644 --- a/drivers/cpufreq/cpufreq_hotplug.c +++ b/drivers/cpufreq/cpufreq_hotplug.c @@ -536,7 +536,6 @@ static void do_dbs_timer(struct work_struct *work) /* We want all related CPUs to do sampling nearly on same jiffy */ int delay = usecs_to_jiffies(dbs_tuners_ins.sampling_rate); - delay -= jiffies % delay; mutex_lock(&dbs_info->timer_mutex); dbs_check_cpu(dbs_info); -- cgit v1.2.3