From: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Linux PM <linux-pm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Zhang Rui <rui.zhang@intel.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: [PATCH v1] cpufreq: intel_pstate: Relocate platform preference check
Date: Thu, 20 Feb 2025 21:39:14 -0800 [thread overview]
Message-ID: <df4fd1434a72f520e34afce386e10890bb4ae073.camel@linux.intel.com> (raw)
In-Reply-To: <CAJZ5v0jF_oLkzqEJuc9NX_j1+javyU8HF0JU8FiFgNaCks+RdA@mail.gmail.com>
On Thu, 2025-02-20 at 20:30 +0100, Rafael J. Wysocki wrote:
> On Fri, Feb 7, 2025 at 1:48 PM Rafael J. Wysocki <rjw@rjwysocki.net>
> wrote:
> >
> > From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> >
> > Move the invocation of intel_pstate_platform_pwr_mgmt_exists()
> > before
> > checking whether or not HWP is enabled because it does not depend
> > on
> > any code running before it except for the vendor check and if CPU
> > performance scaling is going to be carried out by the platform, all
> > of
> > the code that runs before that function (again, except for the
> > vendor
> > check) is redundant.
> >
> > This is not expected to alter any functionality except for the
> > ordering
> > of messages printed by intel_pstate_init() when it is going to
> > return an
> > error before attempting to register the driver.
> >
> > Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>
> Srinivas, I'm wondering if you have any concerns regarding this one?
None.
Acked-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Thanks,
Srinivas
>
> > ---
> > drivers/cpufreq/intel_pstate.c | 18 +++++++++---------
> > 1 file changed, 9 insertions(+), 9 deletions(-)
> >
> > --- a/drivers/cpufreq/intel_pstate.c
> > +++ b/drivers/cpufreq/intel_pstate.c
> > @@ -3688,6 +3688,15 @@
> > if (boot_cpu_data.x86_vendor != X86_VENDOR_INTEL)
> > return -ENODEV;
> >
> > + /*
> > + * The Intel pstate driver will be ignored if the platform
> > + * firmware has its own power management modes.
> > + */
> > + if (intel_pstate_platform_pwr_mgmt_exists()) {
> > + pr_info("P-states controlled by the platform\n");
> > + return -ENODEV;
> > + }
> > +
> > id = x86_match_cpu(hwp_support_ids);
> > if (id) {
> > hwp_forced = intel_pstate_hwp_is_enabled();
> > @@ -3743,15 +3752,6 @@
> > default_driver = &intel_cpufreq;
> >
> > hwp_cpu_matched:
> > - /*
> > - * The Intel pstate driver will be ignored if the platform
> > - * firmware has its own power management modes.
> > - */
> > - if (intel_pstate_platform_pwr_mgmt_exists()) {
> > - pr_info("P-states controlled by the platform\n");
> > - return -ENODEV;
> > - }
> > -
> > if (!hwp_active && hwp_only)
> > return -ENOTSUPP;
> >
> >
> >
> >
> >
prev parent reply other threads:[~2025-02-21 5:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 12:48 [PATCH v1] cpufreq: intel_pstate: Relocate platform preference check Rafael J. Wysocki
2025-02-20 19:30 ` Rafael J. Wysocki
2025-02-21 5:39 ` srinivas pandruvada [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=df4fd1434a72f520e34afce386e10890bb4ae073.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=rui.zhang@intel.com \
/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