From: Randy Dunlap <rdunlap@infradead.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linux PM <linux-pm@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Chen Yu <yu.c.chen@intel.com>
Subject: Re: [PATCH] cpufreq: intel_pstate: hybrid: Fix build with CONFIG_ACPI unset
Date: Wed, 26 May 2021 09:10:26 -0700 [thread overview]
Message-ID: <4f0f3e94-d42a-a0fd-ced6-bd1edd6d471b@infradead.org> (raw)
In-Reply-To: <4337451.LvFx2qVVIh@kreacher>
On 5/26/21 8:01 AM, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>
> One of the previous commits introducing hybrid processor support to
> intel_pstate broke build with CONFIG_ACPI unset.
>
> Fix that and while at it fix up empty stubs of two functions related
> to ACPI CPPC.
>
> Fixes: eb3693f0521e ("cpufreq: intel_pstate: hybrid: CPU-specific scaling factor")
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Hi Rafael,
I still have this build error:
../drivers/cpufreq/intel_pstate.c: In function ‘show_base_frequency’:
../drivers/cpufreq/intel_pstate.c:950:10: error: implicit declaration of function ‘intel_pstate_get_cppc_guranteed’; did you mean ‘intel_pstate_get_epp’? [-Werror=implicit-function-declaration]
ratio = intel_pstate_get_cppc_guranteed(policy->cpu);
BTW: s/guranteed/guaranteed/g
Thanks.
> ---
> drivers/cpufreq/intel_pstate.c | 97 +++++++++++++++++++++--------------------
> 1 file changed, 50 insertions(+), 47 deletions(-)
>
> Index: linux-pm/drivers/cpufreq/intel_pstate.c
> ===================================================================
> --- linux-pm.orig/drivers/cpufreq/intel_pstate.c
> +++ linux-pm/drivers/cpufreq/intel_pstate.c
> @@ -385,9 +385,14 @@ static int intel_pstate_get_cppc_gurante
> }
>
> #else /* CONFIG_ACPI_CPPC_LIB */
> -static void intel_pstate_set_itmt_prio(int cpu)
> +static inline void intel_pstate_set_itmt_prio(int cpu)
> {
> }
> +
> +static inline int intel_pstate_get_cppc_guranteed(int cpu)
> +{
> + return -ENOTSUPP;
> +}
> #endif /* CONFIG_ACPI_CPPC_LIB */
>
> static void intel_pstate_init_acpi_perf_limits(struct cpufreq_policy *policy)
> @@ -470,27 +475,6 @@ static void intel_pstate_exit_perf_limit
>
> acpi_processor_unregister_performance(policy->cpu);
> }
> -#else /* CONFIG_ACPI */
> -static inline void intel_pstate_init_acpi_perf_limits(struct cpufreq_policy *policy)
> -{
> -}
> -
> -static inline void intel_pstate_exit_perf_limits(struct cpufreq_policy *policy)
> -{
> -}
> -
> -static inline bool intel_pstate_acpi_pm_profile_server(void)
> -{
> - return false;
> -}
> -#endif /* CONFIG_ACPI */
> -
> -#ifndef CONFIG_ACPI_CPPC_LIB
> -static int intel_pstate_get_cppc_guranteed(int cpu)
> -{
> - return -ENOTSUPP;
> -}
> -#endif /* CONFIG_ACPI_CPPC_LIB */
>
> static bool intel_pstate_cppc_perf_valid(u32 perf, struct cppc_perf_caps *caps)
> {
> @@ -505,6 +489,20 @@ static bool intel_pstate_cppc_perf_caps(
>
> return caps->highest_perf && caps->lowest_perf <= caps->highest_perf;
> }
> +#else /* CONFIG_ACPI */
> +static inline void intel_pstate_init_acpi_perf_limits(struct cpufreq_policy *policy)
> +{
> +}
> +
> +static inline void intel_pstate_exit_perf_limits(struct cpufreq_policy *policy)
> +{
> +}
> +
> +static inline bool intel_pstate_acpi_pm_profile_server(void)
> +{
> + return false;
> +}
> +#endif /* CONFIG_ACPI */
>
> static void intel_pstate_hybrid_hwp_perf_ctl_parity(struct cpudata *cpu)
> {
> @@ -530,7 +528,6 @@ static void intel_pstate_hybrid_hwp_perf
> */
> static void intel_pstate_hybrid_hwp_calibrate(struct cpudata *cpu)
> {
> - struct cppc_perf_caps caps;
> int perf_ctl_max_phys = cpu->pstate.max_pstate_physical;
> int perf_ctl_scaling = cpu->pstate.perf_ctl_scaling;
> int perf_ctl_turbo = pstate_funcs.get_turbo();
> @@ -548,33 +545,39 @@ static void intel_pstate_hybrid_hwp_cali
> pr_debug("CPU%d: HWP_CAP guaranteed = %d\n", cpu->cpu, cpu->pstate.max_pstate);
> pr_debug("CPU%d: HWP_CAP highest = %d\n", cpu->cpu, cpu->pstate.turbo_pstate);
>
> - if (intel_pstate_cppc_perf_caps(cpu, &caps)) {
> - if (intel_pstate_cppc_perf_valid(caps.nominal_perf, &caps)) {
> - pr_debug("CPU%d: Using CPPC nominal\n", cpu->cpu);
> -
> - /*
> - * If the CPPC nominal performance is valid, it can be
> - * assumed to correspond to cpu_khz.
> - */
> - if (caps.nominal_perf == perf_ctl_max_phys) {
> - intel_pstate_hybrid_hwp_perf_ctl_parity(cpu);
> - return;
> - }
> - scaling = DIV_ROUND_UP(cpu_khz, caps.nominal_perf);
> - } else if (intel_pstate_cppc_perf_valid(caps.guaranteed_perf, &caps)) {
> - pr_debug("CPU%d: Using CPPC guaranteed\n", cpu->cpu);
> -
> - /*
> - * If the CPPC guaranteed performance is valid, it can
> - * be assumed to correspond to max_freq.
> - */
> - if (caps.guaranteed_perf == perf_ctl_max) {
> - intel_pstate_hybrid_hwp_perf_ctl_parity(cpu);
> - return;
> +#ifdef CONFIG_ACPI
> + if (IS_ENABLED(CONFIG_ACPI_CPPC_LIB)) {
> + struct cppc_perf_caps caps;
> +
> + if (intel_pstate_cppc_perf_caps(cpu, &caps)) {
> + if (intel_pstate_cppc_perf_valid(caps.nominal_perf, &caps)) {
> + pr_debug("CPU%d: Using CPPC nominal\n", cpu->cpu);
> +
> + /*
> + * If the CPPC nominal performance is valid, it
> + * can be assumed to correspond to cpu_khz.
> + */
> + if (caps.nominal_perf == perf_ctl_max_phys) {
> + intel_pstate_hybrid_hwp_perf_ctl_parity(cpu);
> + return;
> + }
> + scaling = DIV_ROUND_UP(cpu_khz, caps.nominal_perf);
> + } else if (intel_pstate_cppc_perf_valid(caps.guaranteed_perf, &caps)) {
> + pr_debug("CPU%d: Using CPPC guaranteed\n", cpu->cpu);
> +
> + /*
> + * If the CPPC guaranteed performance is valid,
> + * it can be assumed to correspond to max_freq.
> + */
> + if (caps.guaranteed_perf == perf_ctl_max) {
> + intel_pstate_hybrid_hwp_perf_ctl_parity(cpu);
> + return;
> + }
> + scaling = DIV_ROUND_UP(max_freq, caps.guaranteed_perf);
> }
> - scaling = DIV_ROUND_UP(max_freq, caps.guaranteed_perf);
> }
> }
> +#endif
> /*
> * If using the CPPC data to compute the HWP-to-frequency scaling factor
> * doesn't work, use the HWP_CAP gauranteed perf for this purpose with
>
>
>
--
~Randy
next prev parent reply other threads:[~2021-05-26 16:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 15:01 [PATCH] cpufreq: intel_pstate: hybrid: Fix build with CONFIG_ACPI unset Rafael J. Wysocki
2021-05-26 16:10 ` Randy Dunlap [this message]
2021-05-26 17:12 ` 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=4f0f3e94-d42a-a0fd-ced6-bd1edd6d471b@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=yu.c.chen@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;
as well as URLs for NNTP newsgroup(s).