From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: rjw@rjwysocki.net
Cc: linux-pm@vger.kernel.org,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Subject: [PATCH v2 3/4] Documentation: intel_pstate: Update per core limits
Date: Fri, 21 Oct 2016 09:14:25 -0700 [thread overview]
Message-ID: <1477066466-22367-4-git-send-email-srinivas.pandruvada@linux.intel.com> (raw)
In-Reply-To: <1477066466-22367-1-git-send-email-srinivas.pandruvada@linux.intel.com>
Document restriction on per core P-State control.
Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
---
Documentation/cpu-freq/intel-pstate.txt | 23 ++++++++++++++++++++++-
1 file changed, 22 insertions(+), 1 deletion(-)
diff --git a/Documentation/cpu-freq/intel-pstate.txt b/Documentation/cpu-freq/intel-pstate.txt
index 5528d6d..18156ce 100644
--- a/Documentation/cpu-freq/intel-pstate.txt
+++ b/Documentation/cpu-freq/intel-pstate.txt
@@ -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).
+multi-package system, Refer to later section on placing "Per core 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,27 @@ 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.
+Per core limits
+
+Per core limits are not enabled without kernel command line
+ intel_pstate=per_cpu_perf_limits
+
+When user wants to control performance per core, there are some limitations
+in sysfs control, which are described above.
+- The following controls are not available for both read and write
+ /sys/devices/system/cpu/intel_pstate/max_perf_pct
+ /sys/devices/system/cpu/intel_pstate/min_perf_pct
+- User can change limits using the following, respecting processor
+architecture
+ /sys/devices/system/cpu/cpu*/cpufreq/scaling_max_freq
+ /sys/devices/system/cpu/cpu*/cpufreq/scaling_min_freq
+ /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor
+- User can still observe turbo percent and number of P-States from
+ /sys/devices/system/cpu/intel_pstate/turbo_pct
+ /sys/devices/system/cpu/intel_pstate/num_pstates
+- User can read write system wide turbo status
+ /sys/devices/system/cpu/no_turbo
+
Tuning Intel P-State driver
When the performance can be tuned using PID (Proportional Integral
--
2.7.4
next prev parent reply other threads:[~2016-10-21 16:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 16:14 [PATCH v2 0/4] cpufreq: intel_pstate: Per CPU performance control Srinivas Pandruvada
2016-10-21 16:14 ` [PATCH v2 1/4] cpufreq: intel_pstate: Per CPU P-State limits Srinivas Pandruvada
2016-10-22 1:11 ` Rafael J. Wysocki
2016-10-21 16:14 ` [PATCH v2 2/4] cpufreq: intel_pstate: Reduce impact due to rounding error Srinivas Pandruvada
2016-10-21 16:14 ` Srinivas Pandruvada [this message]
2016-10-22 1:26 ` [PATCH v2 3/4] Documentation: intel_pstate: Update per core limits Rafael J. Wysocki
2016-10-21 16:14 ` [PATCH v2 4/4] Documentation: kernel parameters: per core P-State control Srinivas Pandruvada
2016-10-22 1:28 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1477066466-22367-4-git-send-email-srinivas.pandruvada@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).