From: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
Daniel Lezcano <daniel.lezcano@kernel.org>,
Zhang Rui <rui.zhang@intel.com>,
Lukasz Luba <lukasz.luba@arm.com>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Cc: linux-pm@vger.kernel.org, linux-api@vger.kernel.org,
linux-kernel@vger.kernel.org, ricardo.neri@intel.com,
Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
Subject: [PATCH 07/13] thermal: intel: dpti: Configure the local CPU by value
Date: Mon, 09 Nov 2026 19:36:34 -0800 [thread overview]
Message-ID: <20261109-dpti-custom-cpu-v1-7-ead8e2d2067e@linux.intel.com> (raw)
In-Reply-To: <20261109-dpti-custom-cpu-v1-0-ead8e2d2067e@linux.intel.com>
dpti_config() enables or disables the directed package-level thermal
interrupt (DPTI) on the CPU that runs it. It takes its argument by
pointer because it also serves as an smp_call_function_single()
callback. A caller that only programs its own CPU therefore has to
declare a scratch bool and track which value it holds at each call site.
Rename it to dpti_config_this_cpu() and let it take the setting by value.
Only the callers that reach another CPU need the callback signature;
unmarshal the argument for them in a thin dpti_config_ipi() trampoline.
The scratch bool then exists only where an SMP function call is made.
This also prepares for factoring the hardware programming sequence into a
helper that runs on the local CPU and configures the interrupt the same
way.
No functional change intended: the MSR read-modify-write is unchanged, and
the scratch bools held a known value at every converted call site.
Signed-off-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
---
drivers/thermal/intel/therm_throt.c | 24 ++++++++++++++----------
1 file changed, 14 insertions(+), 10 deletions(-)
diff --git a/drivers/thermal/intel/therm_throt.c b/drivers/thermal/intel/therm_throt.c
index a0a3842e2760..36cdbe0eb6c1 100644
--- a/drivers/thermal/intel/therm_throt.c
+++ b/drivers/thermal/intel/therm_throt.c
@@ -500,9 +500,8 @@ static int dpti_wait_for_ack(void)
return 0;
}
-static void dpti_config(void *info)
+static void dpti_config_this_cpu(bool enable)
{
- bool enable = *((bool *)info);
u64 msr_val;
rdmsrq(MSR_IA32_THERM_INTERRUPT, msr_val);
@@ -515,6 +514,11 @@ static void dpti_config(void *info)
wrmsrq(MSR_IA32_THERM_INTERRUPT, msr_val);
}
+static void dpti_config_ipi(void *info)
+{
+ dpti_config_this_cpu(*((bool *)info));
+}
+
/**
* struct dpti_pkg - Per-package DPTI state
* @owner: CPU currently programmed to receive the package-level
@@ -578,14 +582,13 @@ static void dpti_clear_all(void)
if (dpti_pkgs[i].owner == nr_cpu_ids)
continue;
- smp_call_function_single(dpti_pkgs[i].owner, dpti_config,
+ smp_call_function_single(dpti_pkgs[i].owner, dpti_config_ipi,
&enable, true);
}
}
static int dpti_online(unsigned int cpu)
{
- bool enable = true;
u16 pkg_id;
if (!dpti_supported())
@@ -605,15 +608,14 @@ static int dpti_online(unsigned int cpu)
thermal_clear_package_intr_status(PACKAGE_LEVEL,
PACKAGE_THERM_STATUS_DPTI_ACK);
- dpti_config(&enable);
+ dpti_config_this_cpu(true);
if (!dpti_wait_for_ack()) {
dpti_pkgs[pkg_id].owner = cpu;
return 0;
}
/* Roll back on failure so the package reverts to broadcasting mode. */
- enable = false;
- dpti_config(&enable);
+ dpti_config_this_cpu(false);
return -ETIMEDOUT;
}
@@ -657,7 +659,8 @@ static void dpti_offline(unsigned int cpu)
* but it does not reach this path because all the secondary
* CPUs are offline.
*/
- smp_call_function_single(new_cpu, dpti_config, &enable, true);
+ smp_call_function_single(new_cpu, dpti_config_ipi, &enable,
+ true);
}
/*
@@ -668,7 +671,8 @@ static void dpti_offline(unsigned int cpu)
*/
enable = false;
if (new_cpu < nr_cpu_ids && dpti_wait_for_ack()) {
- smp_call_function_single(new_cpu, dpti_config, &enable, true);
+ smp_call_function_single(new_cpu, dpti_config_ipi, &enable,
+ true);
pr_warn_once("Failed to redirect package thermal interrupt from CPU%u to CPU%u; reverting to broadcast\n",
cpu, new_cpu);
@@ -680,7 +684,7 @@ static void dpti_offline(unsigned int cpu)
* Clear the directed interrupt on @cpu. Hardware acknowledgment can be
* ignored since @cpu is going offline.
*/
- dpti_config(&enable);
+ dpti_config_this_cpu(false);
dpti_pkgs[pkg_id].owner = (new_cpu < nr_cpu_ids) ? new_cpu : nr_cpu_ids;
}
--
2.43.0
next prev parent reply other threads:[~2026-11-10 3:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 3:36 [PATCH 00/13] thermal: intel: dpti: Direct the package thermal interrupt to a chosen CPU Ricardo Neri
2026-11-10 3:36 ` [PATCH 01/13] thermal: intel: Keep directed package interrupts off after syscore shutdown Ricardo Neri
2026-11-10 3:36 ` [PATCH 02/13] thermal: intel: Prefix log messages via pr_fmt() Ricardo Neri
2026-11-10 3:36 ` [PATCH 03/13] thermal: intel: Move the sysfs device helpers next to their callers Ricardo Neri
2026-11-10 3:36 ` [PATCH 04/13] thermal: intel: dpti: Adopt the dpti_ prefix and the owner terminology Ricardo Neri
2026-11-10 3:36 ` [PATCH 05/13] thermal: intel: dpti: Tear down DPTI only during boot Ricardo Neri
2026-11-10 3:36 ` [PATCH 06/13] thermal: intel: dpti: Introduce struct dpti_pkg for per-package state Ricardo Neri
2026-11-10 3:36 ` Ricardo Neri [this message]
2026-11-10 3:36 ` [PATCH 08/13] thermal: intel: dpti: Factor the programming sequence out into a helper Ricardo Neri
2026-11-10 3:36 ` [PATCH 09/13] thermal: intel: dpti: Program the directed interrupt on the target CPU Ricardo Neri
2026-11-10 3:36 ` [PATCH 10/13] thermal: intel: dpti: Add rank-based owner selection Ricardo Neri
2026-11-10 3:36 ` [PATCH 11/13] thermal: intel: dpti: Serialize updates to the directed interrupt state Ricardo Neri
2026-11-10 3:36 ` [PATCH 12/13] thermal: intel: dpti: Avoid nohz_full CPUs when possible Ricardo Neri
2026-11-10 3:36 ` [PATCH 13/13] thermal: intel: dpti: Add sysfs control of interrupt owner Ricardo Neri
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=20261109-dpti-custom-cpu-v1-7-ead8e2d2067e@linux.intel.com \
--to=ricardo.neri-calderon@linux.intel.com \
--cc=daniel.lezcano@kernel.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=rafael@kernel.org \
--cc=ricardo.neri@intel.com \
--cc=rui.zhang@intel.com \
--cc=srinivas.pandruvada@linux.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
all inboxes | Powered by JetHome®