From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: khlebnikov@yandex-team.ru
Cc: linux-pm@vger.kernel.org,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Subject: [PATCH v2 0/3] Enforce _PPC limits
Date: Fri, 22 Apr 2016 21:03:50 -0700 [thread overview]
Message-ID: <1461384233-24214-1-git-send-email-srinivas.pandruvada@linux.intel.com> (raw)
v2
- kernel command line is changed to support_acpi_ppc from acpi_ppc
- Removed shared_cpu_map allocation, this is only needed if we call
acpi_processor_preregister_performance
- Split the change in the setpolicy callback to another patch
- For enterprise servers and performance servers turns _PPC enforcement
on by default
- Minor fixes for label name and CONFIG_ACPI define
Srinivas Pandruvada (3):
cpufreq: intel_pstate: Enforce _PPC limits
cpufreq: intel_pstate: Adjust policy->max
cpufreq: intel_pstate: Enable PPC enforcement for servers
Documentation/kernel-parameters.txt | 5 ++
drivers/cpufreq/Kconfig.x86 | 1 +
drivers/cpufreq/intel_pstate.c | 164 +++++++++++++++++++++++++++++++++++-
3 files changed, 168 insertions(+), 2 deletions(-)
--
2.5.0
next reply other threads:[~2016-04-23 4:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-23 4:03 Srinivas Pandruvada [this message]
2016-04-23 4:03 ` [PATCH v2 1/3] cpufreq: intel_pstate: Enforce _PPC limits Srinivas Pandruvada
2016-04-23 4:03 ` [PATCH v2 2/3] cpufreq: intel_pstate: Adjust policy->max Srinivas Pandruvada
2016-04-25 10:13 ` Konstantin Khlebnikov
2016-04-25 18:58 ` Srinivas Pandruvada
2016-04-25 21:24 ` Rafael J. Wysocki
2016-04-23 4:03 ` [PATCH v2 3/3] cpufreq: intel_pstate: Enable PPC enforcement for servers Srinivas Pandruvada
-- strict thread matches above, loose matches on Subject: below --
2016-04-23 4:01 [PATCH v2 0/3] Enforce _PPC limits 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=1461384233-24214-1-git-send-email-srinivas.pandruvada@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=khlebnikov@yandex-team.ru \
--cc=linux-pm@vger.kernel.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).