linux-kernel - Re: [PATCH V2 2/3] cpufreq: intel_pstate: Migrate to ->exit() callback instead of ->stop

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAJZ5v0iR2FeKGQRcAFzNWCvkoMOnnGOT6FThK1LBHFt=VWySww@mail.gmail.com>
Date:   Thu, 17 Jun 2021 15:27:07 +0200
From:   "Rafael J. Wysocki" <rafael@...nel.org>
To:     Viresh Kumar <viresh.kumar@...aro.org>
Cc:     Rafael Wysocki <rjw@...ysocki.net>,
        Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>,
        Len Brown <lenb@...nel.org>,
        Linux PM <linux-pm@...r.kernel.org>,
        Vincent Guittot <vincent.guittot@...aro.org>,
        Dirk Brandewie <dirk.brandewie@...il.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH V2 2/3] cpufreq: intel_pstate: Migrate to ->exit()
 callback instead of ->stop_cpu()

On Wed, Jun 16, 2021 at 8:41 AM Viresh Kumar <viresh.kumar@...aro.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 two separate
> callbacks for cpufreq drivers, i.e. stop_cpu() and exit(), as everything
> can be done from the exit() callback itself.
>
> Migrate to using the exit() callback instead of stop_cpu().
>
> Cc: Dirk Brandewie <dirk.brandewie@...il.com>
> Signed-off-by: Viresh Kumar <viresh.kumar@...aro.org>
> ---
>  drivers/cpufreq/intel_pstate.c | 9 +--------
>  1 file changed, 1 insertion(+), 8 deletions(-)
>
> diff --git a/drivers/cpufreq/intel_pstate.c b/drivers/cpufreq/intel_pstate.c
> index 0e69dffd5a76..37ad42926904 100644
> --- a/drivers/cpufreq/intel_pstate.c
> +++ b/drivers/cpufreq/intel_pstate.c
> @@ -2374,17 +2374,11 @@ 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 addresses the ->exit case, but it doesn't address the ->offline
case AFAICS.

>         policy->fast_switch_possible = false;
>
>         return 0;
> @@ -2451,7 +2445,6 @@ static struct cpufreq_driver intel_pstate = {
>         .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,
>         .online         = intel_pstate_cpu_online,
>         .update_limits  = intel_pstate_update_limits,
> --