From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Len Brown <lenb@kernel.org>,
linux-pm@vger.kernel.org,
Vincent Guittot <vincent.guittot@linaro.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V4 2/4] cpufreq: intel_pstate: Migrate to ->offline() instead of ->stop_cpu()
Date: Thu, 24 Jun 2021 07:22:28 +0530 [thread overview]
Message-ID: <20210624015138.nzrrgiqyk3hblknv@vireshk-i7> (raw)
In-Reply-To: <5741915.lOV4Wx5bFT@kreacher>
On 23-06-21, 17:13, Rafael J. Wysocki wrote:
> As mentioned already in
>
> https://lore.kernel.org/linux-pm/CAJZ5v0g2tCZptcqh+c55YYiO7rDHmZivMLsmpq_7005zNPN1xg@mail.gmail.com/
Sorry about failing to reply over that, I got confused somehow..
> this isn't particularly clean, because intel_pstate_cpu_offline() is
> also used in the passive mode where the above call is not needed.
intel_pstate_clear_update_util_hook() returns early if the hook was never
registered, and so calling it was safe, but yes not very clean.
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> Subject: [PATCH] cpufreq: intel_pstate: Combine ->stop_cpu() and ->offline()
>
> Combine the ->stop_cpu() and ->offline() callback routines for the
> active mode of intel_pstate so as to avoid setting the ->stop_cpu
> callback pointer which is going to be dropped from the framework.
>
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> ---
> drivers/cpufreq/intel_pstate.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> Index: linux-pm/drivers/cpufreq/intel_pstate.c
> ===================================================================
> --- linux-pm.orig/drivers/cpufreq/intel_pstate.c
> +++ linux-pm/drivers/cpufreq/intel_pstate.c
> @@ -2577,11 +2577,13 @@ static int intel_pstate_cpu_online(struc
> return 0;
> }
>
> -static void intel_pstate_stop_cpu(struct cpufreq_policy *policy)
> +static int intel_pstate_stop_cpu(struct cpufreq_policy *policy)
> {
> pr_debug("CPU %d stopping\n", policy->cpu);
>
> intel_pstate_clear_update_util_hook(policy->cpu);
> +
> + return intel_pstate_cpu_offline(policy);
> }
>
> static int intel_pstate_cpu_exit(struct cpufreq_policy *policy)
> @@ -2654,8 +2656,7 @@ static struct cpufreq_driver intel_pstat
> .resume = intel_pstate_resume,
> .init = intel_pstate_cpu_init,
> .exit = intel_pstate_cpu_exit,
> - .stop_cpu = intel_pstate_stop_cpu,
> - .offline = intel_pstate_cpu_offline,
> + .offline = intel_pstate_stop_cpu,
I would suggest to rename intel_pstate_cpu_offline() as
intel_cpufreq_cpu_offline() and intel_pstate_stop_cpu() as
intel_pstate_cpu_offline(), so we remove the stop-cpu terminology completely.
Either way:
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
> .online = intel_pstate_cpu_online,
> .update_limits = intel_pstate_update_limits,
> .name = "intel_pstate",
--
viresh
next prev parent reply other threads:[~2021-06-24 1:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 4:24 [PATCH V4 0/4] cpufreq: Migrate away from ->stop_cpu() callback Viresh Kumar
2021-06-23 4:24 ` [PATCH V4 1/4] cpufreq: cppc: Migrate to ->exit() callback instead of ->stop_cpu() Viresh Kumar
2021-06-23 4:24 ` [PATCH V4 2/4] cpufreq: intel_pstate: Migrate to ->offline() " Viresh Kumar
2021-06-23 15:13 ` Rafael J. Wysocki
2021-06-24 1:52 ` Viresh Kumar [this message]
2021-06-30 16:58 ` Rafael J. Wysocki
2021-06-23 4:24 ` [PATCH V4 3/4] cpufreq: powerenv: Migrate to ->exit() callback " Viresh Kumar
2021-06-23 5:45 ` Michael Ellerman
2021-06-23 6:01 ` Viresh Kumar
2021-06-23 6:01 ` [PATCH V4.1 3/4] cpufreq: powernv: " Viresh Kumar
2021-06-23 4:24 ` [PATCH V4 4/4] cpufreq: Remove stop_cpu() callback Viresh Kumar
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=20210624015138.nzrrgiqyk3hblknv@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=vincent.guittot@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).