Linux Power Management development
 help / color / mirror / Atom feed
From: Sumit Gupta <sumitg@nvidia.com>
To: rafael@kernel.org, viresh.kumar@linaro.org,
	pierre.gondois@arm.com, christian.loehle@arm.com,
	ionela.voinescu@arm.com, zhenglifeng1@huawei.com,
	zhanjie9@hisilicon.com, lenb@kernel.org, saket.dumbre@intel.com,
	ray.huang@amd.com, mario.limonciello@amd.com, perry.yuan@amd.com,
	kprateek.nayak@amd.com, linux-kernel@vger.kernel.org,
	linux-pm@vger.kernel.org, linux-acpi@vger.kernel.org,
	acpica-devel@lists.linux.dev, linux-tegra@vger.kernel.org
Cc: treding@nvidia.com, jonathanh@nvidia.com, vsethi@nvidia.com,
	ksitaraman@nvidia.com, sanjayc@nvidia.com, mochs@nvidia.com,
	bbasu@nvidia.com
Subject: Re: [PATCH v4 0/4] cpufreq: CPPC: Preserve OSPM-set registers across hotplug and unload
Date: Wed, 26 Aug 2026 02:50:16 +0530	[thread overview]
Message-ID: <46d81167-1548-4b6a-b6cc-38542b2d093e@nvidia.com> (raw)
In-Reply-To: <20260806200857.601152-1-sumitg@nvidia.com>


On 07/08/26 01:38, Sumit Gupta wrote:
> This series keeps the CPPC cpufreq policy alive across CPU hotplug and
> preserves the OSPM-set CPPC registers (Energy Performance Preference,
> Autonomous Activity Window, Autonomous Selection - set via sysfs).
>
> Without online()/offline() callbacks, the core tears a policy down when
> its last CPU goes offline and rebuilds it on the way back, re-reading the
> CPPC capabilities each time. The values written to these registers can
> be lost:
>
>   - Across CPU hotplug or suspend/resume: the platform may reset them
>     while the CPU is offline.
>   - On driver unload: the driver-written value is left in the register
>     instead of returning to its pre-driver state.
>
> Handle these with:
>
>   - Patch 1: adds online()/offline() callbacks so the core keeps policy
>     alive across CPU hotplug instead of tearing it down and rebuilding it.
>   - Patch 2: makes the autonomous selection register helpers take a u64.
>   - Patch 3: adds a table-driven mechanism that captures each register's
>     firmware value at init(), restores it from offline(), and reapplies
>     the OSPM-set value from online().
>   - Patch 4: extends the same save/restore to system suspend/resume.

Gentle reminder.
Could this be considered for queuing if nothing further needs addressing.

Thanks,
Sumit


> v3[3] -> v4:
>   - Patch 1:
>     - offline() parks the perf request at lowest_perf, as exit() did.
>     - online() resyncs the frequency invariance counters.
>     - raise MAX before the perf restore when the saved MIN is above it.
>   - Patch 3:
>     - write auto_sel first when enabling it and last when disabling it.
>     - replace the four save/restore helpers into save_regs() and
>       apply_saved_regs(), each taking the firmware or requested type.
>     - keep the per-policy saved values in one struct, and name each
>       register for the pr_debug diagnostics.
>   - Patch 4:
>     - suspend() also restores the firmware values and flags it, so
>       offline() skips them and resume() only handles still-online policies.
>
> Sumit Gupta (4):
>    cpufreq: CPPC: Keep the policy across CPU hotplug
>    ACPI: CPPC: Make autonomous selection helpers take a u64
>    cpufreq: CPPC: Preserve OSPM-set registers across hotplug and unload
>    cpufreq: CPPC: Preserve OSPM-set registers across suspend/resume
>
>   drivers/acpi/cppc_acpi.c       |  20 +-
>   drivers/cpufreq/amd-pstate.c   |   2 +-
>   drivers/cpufreq/cppc_cpufreq.c | 369 ++++++++++++++++++++++++++++++++-
>   include/acpi/cppc_acpi.h       |   8 +-
>   4 files changed, 376 insertions(+), 23 deletions(-)
>
> [1] v1: https://lore.kernel.org/lkml/20260623095403.3407436-1-sumitg@nvidia.com/
> [2] v2: https://lore.kernel.org/lkml/20260716153820.2007095-1-sumitg@nvidia.com/
> [3] v3: https://lore.kernel.org/lkml/20260724215937.3368276-1-sumitg@nvidia.com/
>

  parent reply	other threads:[~2026-08-25 21:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-06 20:08 [PATCH v4 0/4] cpufreq: CPPC: Preserve OSPM-set registers across hotplug and unload Sumit Gupta
2026-08-06 20:08 ` [PATCH v4 1/4] cpufreq: CPPC: Keep the policy across CPU hotplug Sumit Gupta
2026-08-06 20:08 ` [PATCH v4 2/4] ACPI: CPPC: Make autonomous selection helpers take a u64 Sumit Gupta
2026-08-06 20:08 ` [PATCH v4 3/4] cpufreq: CPPC: Preserve OSPM-set registers across hotplug and unload Sumit Gupta
2026-08-06 20:08 ` [PATCH v4 4/4] cpufreq: CPPC: Preserve OSPM-set registers across suspend/resume Sumit Gupta
2026-08-25 21:20 ` Sumit Gupta [this message]
2026-08-26  9:07   ` [PATCH v4 0/4] cpufreq: CPPC: Preserve OSPM-set registers across hotplug and unload Christian Loehle
2026-08-26 10:27     ` Rafael J. Wysocki (Intel)
2026-08-26 19:56       ` Sumit 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=46d81167-1548-4b6a-b6cc-38542b2d093e@nvidia.com \
    --to=sumitg@nvidia.com \
    --cc=acpica-devel@lists.linux.dev \
    --cc=bbasu@nvidia.com \
    --cc=christian.loehle@arm.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=mario.limonciello@amd.com \
    --cc=mochs@nvidia.com \
    --cc=perry.yuan@amd.com \
    --cc=pierre.gondois@arm.com \
    --cc=rafael@kernel.org \
    --cc=ray.huang@amd.com \
    --cc=saket.dumbre@intel.com \
    --cc=sanjayc@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