All of lore.kernel.org
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Rafael Wysocki <rjw@rjwysocki.net>,
	Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
	Len Brown <lenb@kernel.org>, Linux PM <linux-pm@vger.kernel.org>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Dirk Brandewie <dirk.brandewie@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V3 2/3] cpufreq: intel_pstate: Migrate away from ->stop_cpu() callback
Date: Mon, 21 Jun 2021 08:39:49 +0530	[thread overview]
Message-ID: <20210621030949.tng5xzq7dm7ngaez@vireshk-i7> (raw)
In-Reply-To: <CAJZ5v0h37bs0xLUCeD7ZuZfXLPBx=6Mpr-Y+Ef=qcnDA4aoLbQ@mail.gmail.com>

On 18-06-21, 14:00, Rafael J. Wysocki wrote:
> On Fri, Jun 18, 2021 at 5:22 AM Viresh Kumar <viresh.kumar@linaro.org> wrote:
> >
> > commit 367dc4aa932b ("cpufreq: Add stop CPU callback to cpufreq_driver
> > interface") added the stop_cpu() callback to allow the drivers to do
> > clean up before the CPU is completely down and its state can't be
> > modified.
> >
> > At that time the CPU hotplug framework used to call the cpufreq core's
> > registered notifier for different events like CPU_DOWN_PREPARE and
> > CPU_POST_DEAD. The stop_cpu() callback was called during the
> > CPU_DOWN_PREPARE event.
> >
> > This is no longer the case, cpuhp_cpufreq_offline() is called only once
> > by the CPU hotplug core now and we don't really need to separately
> > call stop_cpu() for cpufreq drivers.
> >
> > Migrate to using the exit() and offline() callbacks instead of
> > stop_cpu().
> >
> > We need to clear util hook from both the callbacks, exit() and
> > offline(), since it is possible that only exit() gets called sometimes
> > (specially on errors) or both get called at other times.
> > intel_pstate_clear_update_util_hook() anyway have enough protection in
> > place if it gets called a second time and will return early then.
> >
> > Cc: Dirk Brandewie <dirk.brandewie@gmail.com>
> > Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> > ---
> > V2->V3:
> > - Update intel_pstate_cpu_offline() as well.
> > - Improved commit log.
> >
> >  drivers/cpufreq/intel_pstate.c | 12 ++++--------
> >  1 file changed, 4 insertions(+), 8 deletions(-)
> >
> > diff --git a/drivers/cpufreq/intel_pstate.c b/drivers/cpufreq/intel_pstate.c
> > index 0e69dffd5a76..8f8a2d9d7daa 100644
> > --- a/drivers/cpufreq/intel_pstate.c
> > +++ b/drivers/cpufreq/intel_pstate.c
> > @@ -2335,6 +2335,8 @@ static int intel_pstate_cpu_offline(struct cpufreq_policy *policy)
> >
> >         pr_debug("CPU %d going offline\n", cpu->cpu);
> >
> > +       intel_pstate_clear_update_util_hook(policy->cpu);
> > +
> >         if (cpu->suspended)
> >                 return 0;
> >
> > @@ -2374,17 +2376,12 @@ static int intel_pstate_cpu_online(struct cpufreq_policy *policy)
> >         return 0;
> >  }
> >
> > -static void intel_pstate_stop_cpu(struct cpufreq_policy *policy)
> > -{
> > -       pr_debug("CPU %d stopping\n", policy->cpu);
> > -
> > -       intel_pstate_clear_update_util_hook(policy->cpu);
> > -}
> > -
> >  static int intel_pstate_cpu_exit(struct cpufreq_policy *policy)
> >  {
> >         pr_debug("CPU %d exiting\n", policy->cpu);
> >
> > +       intel_pstate_clear_update_util_hook(policy->cpu);
> 
> This change is not needed now, because ->offline always runs before
> ->exit if present.

Not necessarily, we don't call ->offline() for many error paths in
cpufreq_online(). offline() only comes into play after driver is registered
properly once.

-- 
viresh

  reply	other threads:[~2021-06-21  3:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-16  6:40 [PATCH V2 0/3] cpufreq: " Viresh Kumar
2021-06-16  6:40 ` Viresh Kumar
2021-06-16  6:40 ` [PATCH V2 1/3] cpufreq: cppc: Migrate to ->exit() callback instead of ->stop_cpu() Viresh Kumar
2021-06-16  6:40 ` [PATCH V2 2/3] cpufreq: intel_pstate: " Viresh Kumar
2021-06-17 13:27   ` Rafael J. Wysocki
2021-06-18  3:22   ` [PATCH V3 2/3] cpufreq: intel_pstate: Migrate away from ->stop_cpu() callback Viresh Kumar
2021-06-18 12:00     ` Rafael J. Wysocki
2021-06-21  3:09       ` Viresh Kumar [this message]
2021-06-21 14:17         ` Rafael J. Wysocki
2021-06-21 14:26           ` Rafael J. Wysocki
2021-06-21 17:14             ` Rafael J. Wysocki
2021-06-16  6:40 ` [PATCH V2 3/3] cpufreq: powerenv: Migrate to ->exit() callback instead of ->stop_cpu() Viresh Kumar
2021-06-16  6:40   ` 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=20210621030949.tng5xzq7dm7ngaez@vireshk-i7 \
    --to=viresh.kumar@linaro.org \
    --cc=dirk.brandewie@gmail.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=srinivas.pandruvada@linux.intel.com \
    --cc=vincent.guittot@linaro.org \
    --subject='Re: [PATCH V3 2/3] cpufreq: intel_pstate: Migrate away from ->stop_cpu() callback' \
    /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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.