|author||Srinivas Pandruvada <firstname.lastname@example.org>||2016-10-25 13:20:42 -0700|
|committer||Rafael J. Wysocki <email@example.com>||2016-11-01 06:04:06 +0100|
Documentation: intel_pstate: Update per core limits
Document restriction on per core P-State control. Signed-off-by: Srinivas Pandruvada <firstname.lastname@example.org> Signed-off-by: Rafael J. Wysocki <email@example.com>
Diffstat (limited to 'Documentation/cpu-freq')
1 files changed, 20 insertions, 1 deletions
diff --git a/Documentation/cpu-freq/intel-pstate.txt b/Documentation/cpu-freq/intel-pstate.txt
index 5528d6d59687..198b2ef88aec 100644
@@ -48,7 +48,7 @@ In addition to the frequency-controlling interfaces provided by the cpufreq
core, the driver provides its own sysfs files to control the P-State selection.
These files have been added to /sys/devices/system/cpu/intel_pstate/.
Any changes made to these files are applicable to all CPUs (even in a
+multi-package system, Refer to later section on placing "Per-CPU limits").
max_perf_pct: Limits the maximum P-State that will be requested by
the driver. It states it as a percentage of the available performance. The
@@ -120,6 +120,25 @@ frequency is fictional for Intel Core processors. Even if the scaling
driver selects a single P-State, the actual frequency the processor
will run at is selected by the processor itself.
+The kernel command line option "intel_pstate=per_cpu_perf_limits" forces
+the intel_pstate driver to use per-CPU performance limits. When it is set,
+the sysfs control interface described above is subject to limitations.
+- The following controls are not available for both read and write
+- The following controls can be used to set performance limits, as far as the
+architecture of the processor permits:
+- User can still observe turbo percent and number of P-States from
+- User can read write system wide turbo status
Tuning Intel P-State driver
When the performance can be tuned using PID (Proportional Integral