Browse Source

[CPUFREQ] Prevent p4-clockmod from auto-binding to the ondemand governor.

The latency of p4-clockmod sucks so hard that scaling on a regular
basis with ondemand is a really bad idea.

Signed-off-by: Matthew Garrett <mjg59@srcf.ucam.org>
Signed-off-by: Dave Jones <davej@redhat.com>
Dave Jones 16 years ago
parent
commit
36e8abf3ed
1 changed files with 4 additions and 1 deletions
  1. 4 1
      arch/x86/kernel/cpu/cpufreq/p4-clockmod.c

+ 4 - 1
arch/x86/kernel/cpu/cpufreq/p4-clockmod.c

@@ -246,7 +246,10 @@ static int cpufreq_p4_cpu_init(struct cpufreq_policy *policy)
 	cpufreq_frequency_table_get_attr(p4clockmod_table, policy->cpu);
 	cpufreq_frequency_table_get_attr(p4clockmod_table, policy->cpu);
 
 
 	/* cpuinfo and default policy values */
 	/* cpuinfo and default policy values */
-	policy->cpuinfo.transition_latency = 1000000; /* assumed */
+
+	/* the transition latency is set to be 1 higher than the maximum
+	 * transition latency of the ondemand governor */
+	policy->cpuinfo.transition_latency = 10000001;
 	policy->cur = stock_freq;
 	policy->cur = stock_freq;
 
 
 	return cpufreq_frequency_table_cpuinfo(policy, &p4clockmod_table[0]);
 	return cpufreq_frequency_table_cpuinfo(policy, &p4clockmod_table[0]);