Commit:     91973de736bc97dc04156242c5a4b00993b6c902
Parent:     aac22d0a79f51d7bd93145be36322baaa4b423f8
Author:     Peter Oruba <[EMAIL PROTECTED]>
AuthorDate: Mon Jul 9 11:35:27 2007 -0700
Committer:  Dave Jones <[EMAIL PROTECTED]>
CommitDate: Fri Jul 13 01:29:51 2007 -0400

    [CPUFREQ] bugfix cpufreq in combination with performance governor
    There is a frequency scaling issue that I encountered with the performance
    governor in combination with CPU hotplug.
    In cpufreq.c CPU frequency is reduced to its minimum before the CPU gets
    unregistered and set offline.  Does that have a particular reason?
    Since the (k8-)governor does not monitor CPU frequency that setting also
    applies then to the remaining CPU as well and lets the system run on the
    lowest frequency although performance is chose as the policy.
    Signed-off-by: Peter Oruba <[EMAIL PROTECTED]>
    Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
    Signed-off-by: Dave Jones <[EMAIL PROTECTED]>
 drivers/cpufreq/cpufreq.c |    6 ------
 1 files changed, 0 insertions(+), 6 deletions(-)

diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
index 0db9e1b..99f9c3c 100644
--- a/drivers/cpufreq/cpufreq.c
+++ b/drivers/cpufreq/cpufreq.c
@@ -1687,7 +1687,6 @@ static int cpufreq_cpu_callback(struct notifier_block 
        unsigned int cpu = (unsigned long)hcpu;
        struct sys_device *sys_dev;
-       struct cpufreq_policy *policy;
        sys_dev = get_cpu_sysdev(cpu);
        if (sys_dev) {
@@ -1701,11 +1700,6 @@ static int cpufreq_cpu_callback(struct notifier_block 
                        if (unlikely(lock_policy_rwsem_write(cpu)))
-                       policy = cpufreq_cpu_data[cpu];
-                       if (policy) {
-                               __cpufreq_driver_target(policy, policy->min,
-                                               CPUFREQ_RELATION_H);
-                       }
                case CPU_DOWN_FAILED:
To unsubscribe from this list: send the line "unsubscribe git-commits-head" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at

Reply via email to