From: Christian Loehle <christian.loehle@arm.com>
To: Sumit Gupta <sumitg@nvidia.com>,
rafael@kernel.org, viresh.kumar@linaro.org,
pierre.gondois@arm.com, ionela.voinescu@arm.com,
zhenglifeng1@huawei.com, zhanjie9@hisilicon.com, lenb@kernel.org,
ray.huang@amd.com, mario.limonciello@amd.com, perry.yuan@amd.com,
kprateek.nayak@amd.com, maciej.wieczor-retman@intel.com,
pawel.chmielewski@intel.com, linux-pm@vger.kernel.org,
linux-acpi@vger.kernel.org, acpica-devel@lists.linux.dev,
linux-kernel@vger.kernel.org
Cc: linux-tegra@vger.kernel.org, treding@nvidia.com,
jonathanh@nvidia.com, vsethi@nvidia.com, ksitaraman@nvidia.com,
sanjayc@nvidia.com, mochs@nvidia.com, bbasu@nvidia.com
Subject: Re: [PATCH v7 2/5] cpufreq: CPPC: Keep the policy across CPU hotplug
Date: Tue, 3 Nov 2026 11:50:02 +0000 [thread overview]
Message-ID: <b56fe695-e626-4335-878d-07a6298954ac@arm.com> (raw)
In-Reply-To: <20261030092416.1993889-2-sumitg@nvidia.com>
On 10/30/26 09:24, Sumit Gupta wrote:
> Without online()/offline() callbacks, the cpufreq core calls exit() when
> a policy's last online CPU goes down. That drops the driver's per-policy
> data, which init() rebuilds when a CPU comes back.
>
> Add lightweight online()/offline() callbacks so the core instead keeps
> the policy active and reuses the driver's cpu_data across CPU hotplug.
> init() then runs once instead of on every hotplug, making CPU hotplug
> faster.
>
> This also lets offline() and online() restore and reapply register
> values across CPU hotplug. A later patch in this series uses this to
> preserve the OSPM-set registers.
>
> Move what init() and exit() did on hotplug into the new callbacks:
>
> - offline() requests the lowest performance and stops the frequency
> invariance updates, as exit() did. It also sets MIN to the lowest
> performance, so that Desired is not below MIN while the CPU is
> offline.
> - online() re-enables CPPC and restores the performance controls, as
> the platform may have reset them. Failures are logged, not returned,
> as the core would free the policy. It also restarts the frequency
> invariance updates with a new counter snapshot, as init() did, so
> that no sample spans the offline window.
> - exit() now only frees the driver data, as the core calls offline()
> before it.
>
> The driver keeps a copy of the MIN and MAX it last wrote, so that
> fast_switch() can skip writing them again. online() marks that copy out
> of date before the restore, as the platform may have reset the limits,
> and updates it once the restore succeeds.
>
> Signed-off-by: Sumit Gupta <sumitg@nvidia.com>
Reviewed-by: Christian Loehle <christian.loehle@arm.com>
> ---
> drivers/cpufreq/cppc_cpufreq.c | 106 ++++++++++++++++++++++++++++++---
> 1 file changed, 97 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/cpufreq/cppc_cpufreq.c b/drivers/cpufreq/cppc_cpufreq.c
> index ded4f935638e..2cf250b38633 100644
> --- a/drivers/cpufreq/cppc_cpufreq.c
> +++ b/drivers/cpufreq/cppc_cpufreq.c
> @@ -209,7 +209,7 @@ static void cppc_cpufreq_cpu_fie_exit(struct cpufreq_policy *policy)
> if (fie_disabled)
> return;
>
> - /* policy->cpus will be empty here, use related_cpus instead */
> + /* policy->cpus has only the online CPUs, so use related_cpus */
> topology_clear_scale_freq_source(SCALE_FREQ_SOURCE_CPPC, policy->related_cpus);
>
> for_each_cpu(cpu, policy->related_cpus) {
> @@ -807,24 +807,110 @@ static int cppc_cpufreq_cpu_init(struct cpufreq_policy *policy)
> }
>
> static void cppc_cpufreq_cpu_exit(struct cpufreq_policy *policy)
> +{
> + /*
> + * The core always calls offline() first, so only the driver data is
> + * left to free.
> + */
> + cppc_cpufreq_put_cpu_data(policy);
> +}
> +
> +/*
> + * Run when the policy's first CPU comes back online, the counterpart of
> + * offline().
> + *
> + * The platform may have disabled CPPC and reset the performance controls
> + * (desired, min and max performance) while the CPU was offline. Re-enable
> + * CPPC and reprogram the controls.
> + *
> + * Log failures but do not return them, as the core would free the policy.
> + * Continue after a failure to enable CPPC, as the writes that follow fail
> + * on their own if the platform does not take them. A failed controls write
> + * is not fatal, as the next frequency change writes the controls again.
> + */
> +static int cppc_cpufreq_cpu_online(struct cpufreq_policy *policy)
> {
> struct cppc_cpudata *cpu_data = policy->driver_data;
> - struct cppc_perf_caps *caps = &cpu_data->perf_caps;
> + u32 desired_perf, min_perf, max_perf;
> + struct cppc_perf_ctrls perf_ctrls = {};
> + unsigned int cpu = policy->cpu;
> + int ret;
> +
> + /*
> + * The platform may have reset MIN and MAX, so mark the copy that
> + * fast_switch() uses as out of date until the restore below succeeds.
> + */
> + WRITE_ONCE(cpu_data->perf_limits_valid, false);
> +
> + ret = cppc_set_enable(cpu, true);
> + if (ret && ret != -EOPNOTSUPP)
> + pr_warn("Failed to re-enable CPPC for CPU%u (%d)\n", cpu, ret);
> +
> + /*
> + * Recompute min/max from the policy, clamp the last request into range,
> + * and reprogram the performance controls. Update the driver's copy only
> + * if the write succeeds. Otherwise the next frequency change writes the
> + * limits again.
> + */
> + cppc_cpufreq_get_perf_limits(cpu_data, policy, &min_perf, &max_perf);
> + desired_perf = clamp_t(u32, cpu_data->perf_ctrls.desired_perf,
> + min_perf, max_perf);
> +
> + perf_ctrls.desired_perf = desired_perf;
> + perf_ctrls.min_perf = min_perf;
> + perf_ctrls.max_perf = max_perf;
> + perf_ctrls.min_perf_valid = true;
> +
> + ret = cppc_set_perf(cpu, &perf_ctrls);
> + if (ret) {
> + pr_debug("Failed to restore perf controls on CPU%u (%d)\n",
> + cpu, ret);
> + } else {
> + WRITE_ONCE(cpu_data->perf_ctrls.desired_perf, desired_perf);
> + WRITE_ONCE(cpu_data->perf_ctrls.min_perf, min_perf);
> + WRITE_ONCE(cpu_data->perf_ctrls.max_perf, max_perf);
> + WRITE_ONCE(cpu_data->perf_limits_valid, true);
> + }
> +
> + /* Restart what offline() stopped, with a new counter snapshot. */
> + cppc_cpufreq_cpu_fie_init(policy);
> +
> + return 0;
> +}
> +
> +/*
> + * Run when the policy's last online CPU goes down, the counterpart of online().
> + * Having offline() makes the core keep the policy rather than call exit().
> + */
> +static int cppc_cpufreq_cpu_offline(struct cpufreq_policy *policy)
> +{
> + struct cppc_cpudata *cpu_data = policy->driver_data;
> + struct cppc_perf_ctrls perf_ctrls = cpu_data->perf_ctrls;
> unsigned int cpu = policy->cpu;
> int ret;
>
> + /*
> + * Stop the frequency invariance updates and cancel the pending work, so
> + * that no sample spans the offline window. online() restarts them with
> + * a new counter snapshot.
> + */
> cppc_cpufreq_cpu_fie_exit(policy);
>
> - cpu_data->perf_ctrls.desired_perf = caps->lowest_perf;
> - cpu_data->perf_ctrls.min_perf = caps->lowest_perf;
> - cpu_data->perf_ctrls.min_perf_valid = true;
> + /*
> + * Request the lowest performance while the policy has no online CPU,
> + * lowering MIN with it so that the request stays a valid tuple. MAX
> + * keeps the value the policy last programmed.
> + */
> + perf_ctrls.desired_perf = cpu_data->perf_caps.lowest_perf;
> + perf_ctrls.min_perf = cpu_data->perf_caps.lowest_perf;
> + perf_ctrls.min_perf_valid = true;
>
> - ret = cppc_set_perf(cpu, &cpu_data->perf_ctrls);
> + ret = cppc_set_perf(cpu, &perf_ctrls);
> if (ret)
> - pr_debug("Err setting perf value:%d on CPU:%d. ret:%d\n",
> - caps->lowest_perf, cpu, ret);
> + pr_debug("Err setting perf value:%u on CPU:%u. ret:%d\n",
> + cpu_data->perf_caps.lowest_perf, cpu, ret);
>
> - cppc_cpufreq_put_cpu_data(policy);
> + return 0;
> }
>
> static int cppc_cpufreq_cpu_resume(struct cpufreq_policy *policy)
> @@ -1141,6 +1227,8 @@ static struct cpufreq_driver cppc_cpufreq_driver = {
> .fast_switch = cppc_cpufreq_fast_switch,
> .init = cppc_cpufreq_cpu_init,
> .exit = cppc_cpufreq_cpu_exit,
> + .online = cppc_cpufreq_cpu_online,
> + .offline = cppc_cpufreq_cpu_offline,
> .resume = cppc_cpufreq_cpu_resume,
> .set_boost = cppc_cpufreq_set_boost,
> .attr = cppc_cpufreq_attr,
next prev parent reply other threads:[~2026-11-03 11:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 9:24 [PATCH v7 0/5] cpufreq: CPPC: Preserve OSPM-set registers across hotplug and unload Sumit Gupta
2026-10-30 9:24 ` [PATCH v7 2/5] cpufreq: CPPC: Keep the policy across CPU hotplug Sumit Gupta
2026-11-03 11:50 ` Christian Loehle [this message]
2026-10-30 9:24 ` [PATCH v7 3/5] ACPI: CPPC: Make autonomous selection helpers take a u64 Sumit Gupta
2026-10-30 9:24 ` [PATCH v7 4/5] cpufreq: CPPC: Preserve OSPM-set registers across hotplug and unload Sumit Gupta
2026-10-30 9:24 ` [PATCH v7 5/5] cpufreq: CPPC: Preserve OSPM-set registers across suspend/resume Sumit Gupta
2026-10-30 9:33 ` [PATCH v7 1/5] ACPI: CPPC: Order performance-control updates Sumit Gupta
2026-11-03 14:11 ` [PATCH v7 0/5] cpufreq: CPPC: Preserve OSPM-set registers across hotplug and unload Christian Loehle
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=b56fe695-e626-4335-878d-07a6298954ac@arm.com \
--to=christian.loehle@arm.com \
--cc=acpica-devel@lists.linux.dev \
--cc=bbasu@nvidia.com \
--cc=ionela.voinescu@arm.com \
--cc=jonathanh@nvidia.com \
--cc=kprateek.nayak@amd.com \
--cc=ksitaraman@nvidia.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=maciej.wieczor-retman@intel.com \
--cc=mario.limonciello@amd.com \
--cc=mochs@nvidia.com \
--cc=pawel.chmielewski@intel.com \
--cc=perry.yuan@amd.com \
--cc=pierre.gondois@arm.com \
--cc=rafael@kernel.org \
--cc=ray.huang@amd.com \
--cc=sanjayc@nvidia.com \
--cc=sumitg@nvidia.com \
--cc=treding@nvidia.com \
--cc=viresh.kumar@linaro.org \
--cc=vsethi@nvidia.com \
--cc=zhanjie9@hisilicon.com \
--cc=zhenglifeng1@huawei.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®