summaryrefslogtreecommitdiffstats
path: root/cpufreq-intel-pstate-max-is-in-the-max-variable-who-knew.patch
diff options
context:
space:
mode:
Diffstat (limited to 'cpufreq-intel-pstate-max-is-in-the-max-variable-who-knew.patch')
-rw-r--r--cpufreq-intel-pstate-max-is-in-the-max-variable-who-knew.patch42
1 files changed, 0 insertions, 42 deletions
diff --git a/cpufreq-intel-pstate-max-is-in-the-max-variable-who-knew.patch b/cpufreq-intel-pstate-max-is-in-the-max-variable-who-knew.patch
deleted file mode 100644
index e0d590b21..000000000
--- a/cpufreq-intel-pstate-max-is-in-the-max-variable-who-knew.patch
+++ /dev/null
@@ -1,42 +0,0 @@
-From: dirk.brandewie@gmail.com
-To: linux-kernel@vger.kernel.org, cpufreq@vger.kernel.org
-Cc: Dirk Brandewie <dirk.brandewie@gmail.com>,
- Dirk Brandewie <dirk.j.brandewie@intel.com>
-Subject: [PATCH] cpufreq/intel_pstate: Fix calculation of current frequency
-Date: Fri, 22 Mar 2013 10:51:05 -0700
-Message-Id: <1363974665-22049-1-git-send-email-dirk.brandewie@gmail.com>
-
-From: Dirk Brandewie <dirk.brandewie@gmail.com>
-
-Use the correct pstate value to calculate the effective frequency.
-
-https://bugzilla.redhat.com/show_bug.cgi?id=923942
-Reported-by: Satish Balay <balay@fastmail.fm>
-
-Signed-off-by: Dirk Brandewie <dirk.j.brandewie@intel.com>
----
- drivers/cpufreq/intel_pstate.c | 2 +-
- 1 files changed, 1 insertions(+), 1 deletions(-)
-
-diff --git a/drivers/cpufreq/intel_pstate.c b/drivers/cpufreq/intel_pstate.c
-index e84af66..ad72922 100644
---- a/drivers/cpufreq/intel_pstate.c
-+++ b/drivers/cpufreq/intel_pstate.c
-@@ -454,7 +454,7 @@ static inline void intel_pstate_calc_busy(struct cpudata *cpu,
- sample->idletime_us * 100,
- sample->duration_us);
- core_pct = div64_u64(sample->aperf * 100, sample->mperf);
-- sample->freq = cpu->pstate.turbo_pstate * core_pct * 1000;
-+ sample->freq = cpu->pstate.max_pstate * core_pct * 1000;
-
- sample->core_pct_busy = div_s64((sample->pstate_pct_busy * core_pct),
- 100);
---
-1.7.7.6
-
---
-To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
-the body of a message to majordomo@vger.kernel.org
-More majordomo info at http://vger.kernel.org/majordomo-info.html
-Please read the FAQ at http://www.tux.org/lkml/
-