From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linux PM <linux-pm@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] cpufreq: intel_pstate: Clean up after performance governor changes
Date: Thu, 29 Jun 2017 14:19:48 -0700 [thread overview]
Message-ID: <1498771188.7952.114.camel@linux.intel.com> (raw)
In-Reply-To: <4550329.lZWPcKkG2D@aspire.rjw.lan>
On Thu, 2017-06-29 at 01:47 +0200, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>
> After commit 82b4e03e01bc (intel_pstate: skip scheduler hook when in
> "performance" mode) get_target_pstate_use_performance() and
> get_target_pstate_use_cpu_load() are never called if scaling_governor
> is "performance", so drop the CPUFREQ_POLICY_PERFORMANCE checks from
> them as they will never trigger anyway.
>
> Moreover, the documentation needs to be updated to reflect the change
> made by the above commit, so do that too.
>
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
> ---
> Documentation/admin-guide/pm/intel_pstate.rst | 6 ++----
> drivers/cpufreq/intel_pstate.c | 6 ------
> 2 files changed, 2 insertions(+), 10 deletions(-)
>
> Index: linux-pm/drivers/cpufreq/intel_pstate.c
> ===================================================================
> --- linux-pm.orig/drivers/cpufreq/intel_pstate.c
> +++ linux-pm/drivers/cpufreq/intel_pstate.c
> @@ -1612,9 +1612,6 @@ static inline int32_t get_target_pstate_
> int32_t busy_frac, boost;
> int target, avg_pstate;
>
> - if (cpu->policy == CPUFREQ_POLICY_PERFORMANCE)
> - return cpu->pstate.turbo_pstate;
> -
> busy_frac = div_fp(sample->mperf, sample->tsc);
>
> boost = cpu->iowait_boost;
> @@ -1651,9 +1648,6 @@ static inline int32_t get_target_pstate_
> int32_t perf_scaled, max_pstate, current_pstate,
> sample_ratio;
> u64 duration_ns;
>
> - if (cpu->policy == CPUFREQ_POLICY_PERFORMANCE)
> - return cpu->pstate.turbo_pstate;
> -
> /*
> * perf_scaled is the ratio of the average P-state during
> the last
> * sampling period to the P-state requested last time (in
> percent).
> Index: linux-pm/Documentation/admin-guide/pm/intel_pstate.rst
> ===================================================================
> --- linux-pm.orig/Documentation/admin-guide/pm/intel_pstate.rst
> +++ linux-pm/Documentation/admin-guide/pm/intel_pstate.rst
> @@ -157,10 +157,8 @@ Without HWP, this P-state selection algo
> the processor model and platform configuration.
>
> It selects the maximum P-state it is allowed to use, subject to
> limits set via
> -``sysfs``, every time the P-state selection computations are carried
> out by the
> -driver's utilization update callback for the given CPU (that does
> not happen
> -more often than every 10 ms), but the hardware configuration will
> not be changed
> -if the new P-state is the same as the current one.
> +``sysfs``, every time the driver configuration for the given CPU is
> updated
> +(e.g. via ``sysfs``).
>
> This is the default P-state selection algorithm if the
> :c:macro:`CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE` kernel
> configuration option
>
next prev parent reply other threads:[~2017-06-29 21:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 23:46 [PATCH 0/2] cpufreq: intel_pstate: Cleanups after recent changes Rafael J. Wysocki
2017-06-28 23:47 ` [PATCH 1/2] cpufreq: intel_pstate: Clean up after performance governor changes Rafael J. Wysocki
2017-06-29 21:19 ` Srinivas Pandruvada [this message]
2017-06-28 23:49 ` [PATCH 2/2] cpufreq: Update scaling_cur_freq documentation 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=1498771188.7952.114.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--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