public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Prarit Bhargava <prarit@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: Prarit Bhargava <prarit@redhat.com>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	Dirk Brandewie <dirk.brandewie@gmail.com>,
	Randy Dunlap <rdunlap@infradead.org>,
	Russell King <linux@arm.linux.org.uk>,
	Jesper Nilsson <jesper.nilsson@axis.com>,
	"David S. Miller" <davem@davemloft.net>,
	Ramkumar Ramachandra <artagnon@gmail.com>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	linux-doc@vger.kernel.org
Subject: [PATCH] Documentation, intel_pstate: Add a description of the intel_pstate internal governors [v2]
Date: Thu,  5 Jun 2014 11:07:12 -0400	[thread overview]
Message-ID: <1401980832-4552-1-git-send-email-prarit@redhat.com> (raw)
In-Reply-To: <CAKohpokDZBfZdpSRN_K_QZWXRHk+jSeZ0e4-iBpoaf=hVJ8F_w@mail.gmail.com>

The current documentation is incomplete wrt the intel_pstate internal
governors.  The confusion comes from the general use internal governors
which also use the names performance and powersave.  This patch
differentiates between the two sets of governors.

Cc: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Dirk Brandewie <dirk.brandewie@gmail.com>
Cc: Randy Dunlap <rdunlap@infradead.org>
Cc: Russell King <linux@arm.linux.org.uk>
Cc: Jesper Nilsson <jesper.nilsson@axis.com>
Cc: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "David S. Miller" <davem@davemloft.net>
Cc: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: linux-doc@vger.kernel.org
Signed-off-by: Prarit Bhargava <prarit@redhat.com>

[v2]: text update
---
 Documentation/cpu-freq/governors.txt    |    2 +-
 Documentation/cpu-freq/intel-pstate.txt |    8 ++++++++
 2 files changed, 9 insertions(+), 1 deletion(-)

diff --git a/Documentation/cpu-freq/governors.txt b/Documentation/cpu-freq/governors.txt
index 77ec215..c15aa75 100644
--- a/Documentation/cpu-freq/governors.txt
+++ b/Documentation/cpu-freq/governors.txt
@@ -36,7 +36,7 @@ Contents:
 1. What Is A CPUFreq Governor?
 ==============================
 
-Most cpufreq drivers (in fact, all except one, longrun) or even most
+Most cpufreq drivers (except the intel_pstate and longrun) or even most
 cpu frequency scaling algorithms only offer the CPU to be set to one
 frequency. In order to offer dynamic frequency scaling, the cpufreq
 core must be able to tell these drivers of a "target frequency". So
diff --git a/Documentation/cpu-freq/intel-pstate.txt b/Documentation/cpu-freq/intel-pstate.txt
index e742d21..2edd8d9 100644
--- a/Documentation/cpu-freq/intel-pstate.txt
+++ b/Documentation/cpu-freq/intel-pstate.txt
@@ -9,6 +9,14 @@ assumed to implement internal governors by the cpufreq core. All the
 logic for selecting the current P state is contained within the
 driver; no external governor is used by the cpufreq core.
 
+The Intel P-state driver has two internal governors, performance and
+powersave.  These governors differ from the generally used governors of the
+same name in the kernel.  The internal performance governor sets the
+max_perf_pct and min_perf_pct to 100; that is, the governor selects the
+highest available P state to maximize the performance of the core.  The
+internal powersave governor, selects the appropriate P state based on the
+current load on the CPU.
+
 Intel SandyBridge+ processors are supported.
 
 New sysfs files for controlling P state selection have been added to
-- 
1.7.9.3


  reply	other threads:[~2014-06-05 15:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-05 13:43 [PATCH] Documentation, intel_pstate: Add a description of the intel_pstate internal governors Prarit Bhargava
2014-06-05 14:17 ` Viresh Kumar
2014-06-05 15:07   ` Prarit Bhargava [this message]
2014-06-05 15:10     ` [PATCH] Documentation, intel_pstate: Add a description of the intel_pstate internal governors [v2] Dirk Brandewie
2014-06-05 16:58     ` Randy Dunlap
2014-06-05 17:21       ` [PATCH] Documentation, intel_pstate: Add a description of the intel_pstate internal governors [v3] Prarit Bhargava

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=1401980832-4552-1-git-send-email-prarit@redhat.com \
    --to=prarit@redhat.com \
    --cc=artagnon@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dirk.brandewie@gmail.com \
    --cc=jesper.nilsson@axis.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=rdunlap@infradead.org \
    --cc=rjw@rjwysocki.net \
    --cc=viresh.kumar@linaro.org \
    /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