From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: kristen.c.accardi@intel.com, rafael.j.wysocki@intel.com,
len.brown@intel.com
Cc: linux-pm@vger.kernel.org,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Subject: [PATCH v1 0/6] Intel P states enhancements
Date: Thu, 27 Aug 2015 18:34:20 -0700 [thread overview]
Message-ID: <1440725666-3550-1-git-send-email-srinivas.pandruvada@linux.intel.com> (raw)
This series enhances Intel P state drivers with the following features:
- When max_perf_pct is reduced in turbo range, we can change the turbo ratios
when platform allows. This is particularly useful in limiting performance with
HWP where whole range is turbo.
- Use Turbo Activation Ratio, when calculating max non turbo P state. This will
show now correct percentage in turbo range
- To calculate busy percent, the estimate is not correct when the max non turbo
is limited by tar, hence using physical max non turbo as before.
- Use ACPI _PSS and _PPC in intel_ptate driver.
- Avoid calculation for P state control value when cpufreq policy requests
frequency limits when matched in _PSS. Sometime calculations causes reduced
control value in boundary conditions.
Although they are independent patches, sending as series to help applying and
testing.
I appreciate review and testing on multiple platforms.
v1:
- Change the command line option to "no_acpi"
- changed kernel parameter documentation file and added "no_acpi" parameter
- pr_debug prefixed with "intel_pstate" as suggested by Doug
- Changed the logic to determine turbo freq in _PSS using odd/even convention,
although this is the way it is defined in _PSS. But atleast two reviewers has
questioned the source of this. This is defined usually in non public documents
like BIOS writer guides. Now using the control field value to determine the
turbo and non turbo max.
- Fix the Kconfig dependency on ACPI for ACPI_PROCESSOR
- multi line comment styles
v0:
Base version
Srinivas Pandruvada (6):
cpufreq: intel_p_state: Fix limiting turbo sub states
cpufreq: intel_pstate: get P1 from TAR when available
cpufreq: intel-pstate: Use separate max pstate for scaling
cpufreq: intel_pstate: Use ACPI perf configuration
Documentation: kernel_parameters for Intel P state driver
cpufreq: intel_pstate: Avoid calculation for max/min
Documentation/kernel-parameters.txt | 3 +
arch/x86/include/asm/msr-index.h | 7 +
drivers/cpufreq/Kconfig.x86 | 1 +
drivers/cpufreq/intel_pstate.c | 335 ++++++++++++++++++++++++++++++++++--
4 files changed, 336 insertions(+), 10 deletions(-)
--
2.4.3
next reply other threads:[~2015-08-28 1:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-28 1:34 Srinivas Pandruvada [this message]
2015-08-28 1:34 ` [PATCH v1 1/6] cpufreq: intel_p_state: Fix limiting turbo sub states Srinivas Pandruvada
2015-08-28 1:34 ` [PATCH v1 2/6] cpufreq: intel_pstate: get P1 from TAR when available Srinivas Pandruvada
2015-08-28 1:34 ` [PATCH v1 3/6] cpufreq: intel-pstate: Use separate max pstate for scaling Srinivas Pandruvada
2015-08-28 1:34 ` [PATCH v1 4/6] cpufreq: intel_pstate: Use ACPI perf configuration Srinivas Pandruvada
2015-08-28 1:34 ` [PATCH v1 5/6] Documentation: kernel_parameters for Intel P state driver Srinivas Pandruvada
2015-08-28 1:34 ` [PATCH v1 6/6] cpufreq: intel_pstate: Avoid calculation for max/min 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=1440725666-3550-1-git-send-email-srinivas.pandruvada@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=kristen.c.accardi@intel.com \
--cc=len.brown@intel.com \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
/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).