mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Wyes Karny <wyes.karny@amd.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: ray.huang@amd.com, viresh.kumar@linaro.org,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	gautham.shenoy@amd.com
Subject: Re: [PATCH v4 3/3] cpufreq: Return failure if fast_switch is not set and fast_switch_possible is set
Date: Mon, 29 May 2023 19:38:43 +0530	[thread overview]
Message-ID: <ZHSx61V6fgMcXsvh@BLR-5CG13462PL.amd.com> (raw)
In-Reply-To: <CAJZ5v0gte_QAt1MXXXhpGUTEAC3Eo8LCY6N+=uSFi0NRBG-Omw@mail.gmail.com>

Hi Rafael,

On 24 May 19:44, Rafael J. Wysocki wrote:
> On Wed, May 17, 2023 at 6:30 PM Wyes Karny <wyes.karny@amd.com> wrote:
> >
> > If fast_switch_possible flag is set by the scaling driver, the governor
> > is free to select fast_switch function even if adjust_perf is set.  Some
> > scaling drivers which use adjust_perf don't set fast_switch thinking
> > that the governor would never fall back to fast_switch. But the governor
> > can fall back to fast_switch even in runtime if frequency invariance is
> > disabled due to some reason. This could crash the kernel if the driver
> > didn't set the fast_switch function pointer.
> >
> > Therefore, return failure in cpufreq_online function if fast_switch is
> > not set and fast_switch_possible is set.
> >
> > Signed-off-by: Wyes Karny <wyes.karny@amd.com>
> > ---
> >  drivers/cpufreq/cpufreq.c | 5 +++++
> >  include/linux/cpufreq.h   | 4 +++-
> >  2 files changed, 8 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
> > index 6b52ebe5a890..7835ba4fa34c 100644
> > --- a/drivers/cpufreq/cpufreq.c
> > +++ b/drivers/cpufreq/cpufreq.c
> > @@ -1376,6 +1376,11 @@ static int cpufreq_online(unsigned int cpu)
> >                         goto out_free_policy;
> >                 }
> >
> > +               if (policy->fast_switch_possible && !cpufreq_driver->fast_switch) {
> > +                       pr_err("fast_switch_possible is enabled but fast_switch callback is not set\n");
> > +                       ret = -EINVAL;
> > +                       goto out_destroy_policy;
> > +               }
> 
> The driver registration can fail if the driver has ->adjust_perf
> without ->fast_switch.  Then the check above would not be necessary
> any more.

Sure. Will do that.

> 
> >                 /*
> >                  * The initialization has succeeded and the policy is online.
> >                  * If there is a problem with its frequency table, take it
> > diff --git a/include/linux/cpufreq.h b/include/linux/cpufreq.h
> > index 26e2eb399484..8cdf77bb3bc1 100644
> > --- a/include/linux/cpufreq.h
> > +++ b/include/linux/cpufreq.h
> > @@ -340,7 +340,9 @@ struct cpufreq_driver {
> >         /*
> >          * ->fast_switch() replacement for drivers that use an internal
> >          * representation of performance levels and can pass hints other than
> > -        * the target performance level to the hardware.
> > +        * the target performance level to the hardware. If driver is setting this,
> > +        * then it needs to set fast_switch also. Because in certain scenario scale
> > +        * invariance could be disabled and governor can switch back to fast_switch.
> 
> I would say something like "This can only be set if ->fast_switch is
> set too, because in those cases (under specific conditions) scale
> invariance can be disabled, which causes the schedutil governor to
> fall back to the latter."

Sure. Will update and send the updated patch in-reply-to this.

Thanks & Regards,
Wyes

> 
> >          */
> >         void            (*adjust_perf)(unsigned int cpu,
> >                                        unsigned long min_perf,
> > --
> > 2.34.1
> >

  reply	other threads:[~2023-05-29 14:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-17 16:28 [PATCH v4 0/3] cpufreq/amd-pstate: Fix null pointer dereference when frequency invariance is disabled Wyes Karny
2023-05-17 16:28 ` [PATCH v4 1/3] amd_pstate: Add ->fast_switch() callback Wyes Karny
2023-05-24 17:47   ` Rafael J. Wysocki
2023-05-29  6:57     ` Wyes Karny
2023-05-17 16:28 ` [PATCH v4 2/3] cpufreq/amd-pstate: Remove fast_switch_possible flag from active driver Wyes Karny
2023-05-17 16:28 ` [PATCH v4 3/3] cpufreq: Return failure if fast_switch is not set and fast_switch_possible is set Wyes Karny
2023-05-22  8:28   ` kernel test robot
2023-05-24 17:44   ` Rafael J. Wysocki
2023-05-29 14:08     ` Wyes Karny [this message]
2023-05-29 14:25       ` [PATCH v4.1] cpufreq: Fail driver register if it has adjust_perf without fast_switch Wyes Karny
2023-06-15 16:16         ` 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=ZHSx61V6fgMcXsvh@BLR-5CG13462PL.amd.com \
    --to=wyes.karny@amd.com \
    --cc=gautham.shenoy@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=ray.huang@amd.com \
    --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®