mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	linux-pm@vger.kernel.org,
	Vincent Guittot <vincent.guittot@linaro.org>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpufreq: Rename cpufreq_can_do_remote_dvfs()
Date: Thu, 24 May 2018 11:38:03 +0200	[thread overview]
Message-ID: <1931331.r5s70rLt6c@aspire.rjw.lan> (raw)
In-Reply-To: <17700bd99bc34e4e189b94b417591f328005ffbf.1526983276.git.viresh.kumar@linaro.org>

On Tuesday, May 22, 2018 12:01:30 PM CEST Viresh Kumar wrote:
> This routine checks if the CPU running this code belongs to the policy
> of the target CPU or if not, can it do remote DVFS for it remotely. But
> the current name of it implies as if it is only about doing remote
> updates.
> 
> Rename it to make it more relevant.
> 
> Reported-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> ---
>  drivers/cpufreq/cpufreq_governor.c | 2 +-
>  include/linux/cpufreq.h            | 2 +-
>  kernel/sched/cpufreq_schedutil.c   | 2 +-
>  3 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/cpufreq/cpufreq_governor.c b/drivers/cpufreq/cpufreq_governor.c
> index ca38229b045a..871bf9cf55cf 100644
> --- a/drivers/cpufreq/cpufreq_governor.c
> +++ b/drivers/cpufreq/cpufreq_governor.c
> @@ -278,7 +278,7 @@ static void dbs_update_util_handler(struct update_util_data *data, u64 time,
>  	struct policy_dbs_info *policy_dbs = cdbs->policy_dbs;
>  	u64 delta_ns, lst;
>  
> -	if (!cpufreq_can_do_remote_dvfs(policy_dbs->policy))
> +	if (!cpufreq_this_cpu_can_update(policy_dbs->policy))
>  		return;
>  
>  	/*
> diff --git a/include/linux/cpufreq.h b/include/linux/cpufreq.h
> index 87f48dd932eb..882a9b9e34bc 100644
> --- a/include/linux/cpufreq.h
> +++ b/include/linux/cpufreq.h
> @@ -571,7 +571,7 @@ struct governor_attr {
>  			 size_t count);
>  };
>  
> -static inline bool cpufreq_can_do_remote_dvfs(struct cpufreq_policy *policy)
> +static inline bool cpufreq_this_cpu_can_update(struct cpufreq_policy *policy)
>  {
>  	/*
>  	 * Allow remote callbacks if:
> diff --git a/kernel/sched/cpufreq_schedutil.c b/kernel/sched/cpufreq_schedutil.c
> index 2442decbfec7..2145655dbd9e 100644
> --- a/kernel/sched/cpufreq_schedutil.c
> +++ b/kernel/sched/cpufreq_schedutil.c
> @@ -89,7 +89,7 @@ static bool sugov_should_update_freq(struct sugov_policy *sg_policy, u64 time)
>  	 * schedule the kthread.
>  	 */
>  	if (sg_policy->policy->fast_switch_enabled &&
> -	    !cpufreq_can_do_remote_dvfs(sg_policy->policy))
> +	    !cpufreq_this_cpu_can_update(sg_policy->policy))
>  		return false;
>  
>  	if (sg_policy->work_in_progress)
> 

Applied, thanks!

      reply	other threads:[~2018-05-24  9:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-22 10:01 Viresh Kumar
2018-05-24  9:38 ` Rafael J. Wysocki [this message]

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=1931331.r5s70rLt6c@aspire.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=vincent.guittot@linaro.org \
    --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

all inboxes | Powered by JetHome®