From: "Mario Limonciello (AMD) (kernel.org)" <superm1@kernel.org>
To: "Gautham R. Shenoy" <gautham.shenoy@amd.com>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
K Prateek Nayak <kprateek.nayak@amd.com>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v2 9/9] Documentation/amd-pstate: Add documentation for amd_pstate_floor_{freq,count}
Date: Thu, 12 Mar 2026 15:59:37 -0500 [thread overview]
Message-ID: <0afb773d-e971-4129-8246-790ec840699e@kernel.org> (raw)
In-Reply-To: <20260311140116.19604-10-gautham.shenoy@amd.com>
On 3/11/2026 9:01 AM, Gautham R. Shenoy wrote:
> Add documentation for the sysfs files
> /sys/devices/system/cpu/cpufreq/policy*/amd_pstate_floor_freq
> and
> /sys/devices/system/cpu/cpufreq/policy*/amd_pstate_floor_count.
>
> Signed-off-by: Gautham R. Shenoy <gautham.shenoy@amd.com>
Reviewed-by: Mario Limonciello (AMD) <superm1@kernel.org>
> ---
> Documentation/admin-guide/pm/amd-pstate.rst | 32 +++++++++++++++++++++
> 1 file changed, 32 insertions(+)
>
> diff --git a/Documentation/admin-guide/pm/amd-pstate.rst b/Documentation/admin-guide/pm/amd-pstate.rst
> index f566fea6613e6..5fd2a36f8a4b8 100644
> --- a/Documentation/admin-guide/pm/amd-pstate.rst
> +++ b/Documentation/admin-guide/pm/amd-pstate.rst
> @@ -242,6 +242,8 @@ control its functionality at the system level. They are located in the
> /sys/devices/system/cpu/cpufreq/policy0/amd_pstate_hw_prefcore
> /sys/devices/system/cpu/cpufreq/policy0/amd_pstate_lowest_nonlinear_freq
> /sys/devices/system/cpu/cpufreq/policy0/amd_pstate_max_freq
> + /sys/devices/system/cpu/cpufreq/policy0/amd_pstate_floor_freq
> + /sys/devices/system/cpu/cpufreq/policy0/amd_pstate_floor_count
> /sys/devices/system/cpu/cpufreq/policy0/amd_pstate_prefcore_ranking
>
>
> @@ -278,6 +280,36 @@ can change at runtime based on platform conditions. This attribute is
> read-only. This file is only visible on platforms which support the
> preferred core feature.
>
> +``amd_pstate_floor_freq``
> +
> +The floor frequency associated with each CPU. Userspace can write any
> +value between ``cpuinfo_min_freq`` and ``scaling_max_freq`` into this
> +file. When the system is under power or thermal constraints, the
> +platform firmware will attempt to throttle the CPU frequency to the
> +value specified in ``amd_pstate_floor_freq`` before throttling it
> +further. This allows userspace to specify different floor frequencies
> +to different CPUs. For optimal results, threads of the same core
> +should have the same floor frequency value. This file is only visible
> +on platforms that support the CPPC Performance Priority feature.
> +
> +
> +``amd_pstate_floor_count``
> +
> +The number of distinct Floor Performance levels supported by the
> +platform. For example, if this value is 2, then the number of unique
> +values obtained from the command ``cat
> +/sys/devices/system/cpu/cpufreq/policy*/amd_pstate_floor_freq |
> +sort -n | uniq`` should be at most this number for the behavior
> +described in ``amd_pstate_floor_freq`` to take effect. A zero value
> +implies that the platform supports unlimited floor performance levels.
> +This file is only visible on platforms that support the CPPC
> +Performance Priority feature.
> +
> +**Note**: When ``amd_pstate_floor_count`` is non-zero, the frequency to
> +which the CPU is throttled under power or thermal constraints is
> +undefined when the number of unique values of ``amd_pstate_floor_freq``
> +across all CPUs in the system exceeds ``amd_pstate_floor_count``.
> +
> ``energy_performance_available_preferences``
>
> A list of all the supported EPP preferences that could be used for
prev parent reply other threads:[~2026-03-12 20:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 14:01 [PATCH v2 0/9] amd-pstate: Introduce AMD CPPC Performance Priority Gautham R. Shenoy
2026-03-11 14:01 ` [PATCH v2 1/9] amd-pstate: Fix memory leak in amd_pstate_epp_cpu_init() Gautham R. Shenoy
2026-03-11 14:01 ` [PATCH v2 2/9] amd-pstate: Update cppc_req_cached in fast_switch case Gautham R. Shenoy
2026-03-12 20:41 ` Mario Limonciello (AMD) (kernel.org)
2026-03-11 14:01 ` [PATCH v2 3/9] amd-pstate: Make certain freq_attrs conditionally visible Gautham R. Shenoy
2026-03-12 6:49 ` Gautham R. Shenoy
2026-03-12 20:46 ` Mario Limonciello (AMD) (kernel.org)
2026-03-11 14:01 ` [PATCH v2 4/9] x86/cpufeatures: Add AMD CPPC Performance Priority feature Gautham R. Shenoy
2026-03-11 14:01 ` [PATCH v2 5/9] amd-pstate: Add support for CPPC_REQ2 and FLOOR_PERF Gautham R. Shenoy
2026-03-12 20:49 ` Mario Limonciello (AMD) (kernel.org)
2026-03-11 14:01 ` [PATCH v2 6/9] amd-pstate: Add sysfs support for floor_freq and floor_count Gautham R. Shenoy
2026-03-12 20:57 ` Mario Limonciello (AMD) (kernel.org)
2026-03-12 21:24 ` Mario Limonciello (AMD) (kernel.org)
2026-03-11 14:01 ` [PATCH v2 7/9] amd-pstate: Introduce a tracepoint trace_amd_pstate_cppc_req2() Gautham R. Shenoy
2026-03-11 14:01 ` [PATCH v2 8/9] Documentation/amd-pstate: List prefcore related sysfs files Gautham R. Shenoy
2026-03-12 20:58 ` Mario Limonciello
2026-03-11 14:01 ` [PATCH v2 9/9] Documentation/amd-pstate: Add documentation for amd_pstate_floor_{freq,count} Gautham R. Shenoy
2026-03-12 20:59 ` Mario Limonciello (AMD) (kernel.org) [this message]
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=0afb773d-e971-4129-8246-790ec840699e@kernel.org \
--to=superm1@kernel.org \
--cc=corbet@lwn.net \
--cc=gautham.shenoy@amd.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=viresh.kumar@linaro.org \
/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