diff options
| author | Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com> | 2020-08-03 11:37:20 -0700 |
|---|---|---|
| committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2020-08-04 12:43:07 +0200 |
| commit | 4daca379c703ff55edc065e8e5173dcfeecf0148 (patch) | |
| tree | 6b462c299bda80cdd218338e8a54bdbc4527fcee /net/sched/cls_fw.c | |
| parent | 04084978003c1a1810a0b1fea581078106394a32 (diff) | |
cpufreq: intel_pstate: Fix cpuinfo_max_freq when MSR_TURBO_RATIO_LIMIT is 0
The MSR_TURBO_RATIO_LIMIT can be 0. This is not an error. User can update
this MSR via BIOS settings on some systems or can use msr tools to update.
Also some systems boot with value = 0.
This results in display of cpufreq/cpuinfo_max_freq wrong. This value
will be equal to cpufreq/base_frequency, even though turbo is enabled.
But platform will still function normally in HWP mode as we get max
1-core frequency from the MSR_HWP_CAPABILITIES. This MSR is already used
to calculate cpu->pstate.turbo_freq, which is used for to set
policy->cpuinfo.max_freq. But some other places cpu->pstate.turbo_pstate
is used. For example to set policy->max.
To fix this, also update cpu->pstate.turbo_pstate when updating
cpu->pstate.turbo_freq.
Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'net/sched/cls_fw.c')
0 files changed, 0 insertions, 0 deletions