diff options
| author | Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com> | 2017-01-18 10:48:22 -0800 |
|---|---|---|
| committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2017-01-20 03:35:27 +0100 |
| commit | 1443ebbacfd7f8d84fbbbf629ef66a12dc8a4b4e (patch) | |
| tree | def815751417aada210da2d2a2e9467ff8cb467c /kernel/trace/bpf_trace.c | |
| parent | e11b6293a8fcd3f29376808910f49bd82f72b69a (diff) | |
| download | talos-obmc-linux-1443ebbacfd7f8d84fbbbf629ef66a12dc8a4b4e.tar.gz talos-obmc-linux-1443ebbacfd7f8d84fbbbf629ef66a12dc8a4b4e.zip | |
cpufreq: intel_pstate: Fix sysfs limits enforcement for performance policy
A side effect of keeping intel_pstate sysfs limits in sync with cpufreq
is that the now sysfs limits can't enforced under performance policy.
For example, if the max_perf_pct is changed from 100 to 80, this will call
intel_pstate_set_policy(), which will change the max_perf to 100 again for
performance policy. Same issue happens, when no_turbo is set.
This change calculates max and min frequency using sysfs performance
limits in intel_pstate_verify_policy() and adjusts policy limits by
calling cpufreq_verify_within_limits().
Also, it causes the setting of performance limits to be skipped if
no_turbo is set.
Fixes: 111b8b3fe4fa (cpufreq: intel_pstate: Always keep all limits settings in sync)
Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'kernel/trace/bpf_trace.c')
0 files changed, 0 insertions, 0 deletions
