From: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>
To: Xi Ruoyao <xry111@xry111.site>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
Dave Hansen <dave.hansen@linux.intel.com>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpufreq: intel_pstate: Use raw_smp_processor_id() in hwp_get_cpu_scaling()
Date: Sun, 13 Apr 2025 07:44:56 -0700 [thread overview]
Message-ID: <b7b0b3f98f8fad9cc9559e1c4ce832387c520d7a.camel@linux.intel.com> (raw)
In-Reply-To: <20250412103434.5321-1-xry111@xry111.site>
On Sat, 2025-04-12 at 18:34 +0800, Xi Ruoyao wrote:
> Use raw_smp_processor_id() instead of plain smp_processor_id() in
> hwp_get_cpu_scaling(), otherwise we get some errors on a Lenovo
> Thinkpad
> T14P Gen 2:
>
> BUG: using smp_processor_id() in preemptible [00000000] code:
> swapper/0/1
> caller is hwp_get_cpu_scaling+0x7f/0xc0
>
> Fixes: b52aaeeadfac ("cpufreq: intel_pstate: Avoid SMP calls to get
> cpu-type")
> Signed-off-by: Xi Ruoyao <xry111@xry111.site>
Acked-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
> ---
> drivers/cpufreq/intel_pstate.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/cpufreq/intel_pstate.c
> b/drivers/cpufreq/intel_pstate.c
> index 4aad79d26c64..bfc20b978240 100644
> --- a/drivers/cpufreq/intel_pstate.c
> +++ b/drivers/cpufreq/intel_pstate.c
> @@ -2209,7 +2209,7 @@ static int knl_get_turbo_pstate(int cpu)
> static int hwp_get_cpu_scaling(int cpu)
> {
> if (hybrid_scaling_factor) {
> - struct cpuinfo_x86 *c =
> &cpu_data(smp_processor_id());
> + struct cpuinfo_x86 *c =
> &cpu_data(raw_smp_processor_id());
> u8 cpu_type = c->topo.intel_type;
>
> /*
next prev parent reply other threads:[~2025-04-13 14:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-12 10:34 [PATCH] cpufreq: intel_pstate: Use raw_smp_processor_id() in hwp_get_cpu_scaling() Xi Ruoyao
2025-04-13 14:44 ` srinivas pandruvada [this message]
2025-04-14 15:19 ` Rafael J. Wysocki
2025-04-14 15:26 ` srinivas pandruvada
2025-04-14 15:27 ` Rafael J. Wysocki
2025-04-14 16:41 ` Pawan Gupta
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=b7b0b3f98f8fad9cc9559e1c4ce832387c520d7a.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=rafael@kernel.org \
--cc=xry111@xry111.site \
/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