From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: rafael.j.wysocki@intel.com, viresh.kumar@linaro.org
Cc: linux-pm@vger.kernel.org, prarit@redhat.com, trenn@suse.de,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Subject: [PATCH v2 0/4] cpufreq governors and Intel P state driver compatibility
Date: Tue, 8 Dec 2015 14:31:26 -0800 [thread overview]
Message-ID: <1449613890-10403-1-git-send-email-srinivas.pandruvada@linux.intel.com> (raw)
Intel P State driver implements two policies, performance and powersave.
The powersave policy is similar to ondemand cpufreq governor when using
acpi-cpufreq. This causes lots of confusion among users. This results
in invalid comparison of performance when acpi-cpufreq and Intel P state
performance is compared.
The reason Intel P state called powersave when it actually implemented
ondemand style P State selection, because the cpufreq core only allows
two generic policies "performance and powersave" for drivers which has
setpolicy() interface. All drivers using this interface are forced to
support these two policies.
This patchset adds feature to have configurable generic policies and
allows ondemand as one of the policy. With this approach, Intel P state
now adds support for ondemand policy and power save policy both in
addition to performance.
v2
- Suggestion by Viresh to remove callback to get policies
- Document update for cpufreq cpu-drivers
- Dropped powersave patch, so that it will still default to ondemand
as a possible option suggested by Thomas.
If it breaks any distros are user, who were using Intel P state driver with
powersave, please comment.
v1
base version
To be done:
Intel P state document update
Srinivas Pandruvada (4):
cpufreq: Add configurable generic policies
cpufreq: Add ondemand as a generic policy
Documentation: cpu-freq: update setpolicy documentation
cpufreq: intel_pstate: Change powersave to ondemand policy
Documentation/cpu-freq/cpu-drivers.txt | 9 +++++++--
drivers/cpufreq/cpufreq.c | 17 ++++++++++++++++-
drivers/cpufreq/intel_pstate.c | 14 ++++++++------
include/linux/cpufreq.h | 4 +++-
4 files changed, 34 insertions(+), 10 deletions(-)
--
2.4.3
next reply other threads:[~2015-12-08 22:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 22:31 Srinivas Pandruvada [this message]
2015-12-08 22:31 ` [PATCH v2 1/4] cpufreq: Add configurable generic policies Srinivas Pandruvada
2015-12-09 2:18 ` Viresh Kumar
2015-12-08 22:31 ` [PATCH v2 2/4] cpufreq: Add ondemand as a generic policy Srinivas Pandruvada
2015-12-08 22:31 ` [PATCH v2 3/4] Documentation: cpu-freq: update setpolicy documentation Srinivas Pandruvada
2015-12-09 2:19 ` Viresh Kumar
2015-12-08 22:31 ` [PATCH v2 4/4] cpufreq: intel_pstate: Change powersave to ondemand policy Srinivas Pandruvada
2015-12-08 23:45 ` [PATCH v2 0/4] cpufreq governors and Intel P state driver compatibility Prarit Bhargava
2015-12-08 23:57 ` Srinivas Pandruvada
2015-12-09 13:12 ` Prarit Bhargava
2015-12-09 16:18 ` Srinivas Pandruvada
2015-12-16 19:33 ` Srinivas Pandruvada
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=1449613890-10403-1-git-send-email-srinivas.pandruvada@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=linux-pm@vger.kernel.org \
--cc=prarit@redhat.com \
--cc=rafael.j.wysocki@intel.com \
--cc=trenn@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).