From: Sumit Gupta <sumitg@nvidia.com>
To: Mario Limonciello <superm1@kernel.org>,
linux-doc@vger.kernel.org, corbet@lwn.net,
Randy Dunlap <rdunlap@infradead.org>
Cc: linux-tegra@vger.kernel.org, treding@nvidia.com,
jonathanh@nvidia.com, vsethi@nvidia.com, ksitaraman@nvidia.com,
sanjayc@nvidia.com, bbasu@nvidia.com, rafael@kernel.org,
viresh.kumar@linaro.org, lenb@kernel.org, robert.moore@intel.com,
pierre.gondois@arm.com, zhenglifeng1@huawei.com,
ray.huang@amd.com, gautham.shenoy@amd.com, perry.yuan@amd.com,
linux-pm@vger.kernel.org, linux-acpi@vger.kernel.org,
acpica-devel@lists.linux.dev, linux-kernel@vger.kernel.org,
sumitg@nvidia.com
Subject: Re: [PATCH v3 6/8] cpufreq: CPPC: Add sysfs for min/max_perf and perf_limited
Date: Wed, 8 Oct 2025 15:46:29 +0530 [thread overview]
Message-ID: <b7b137d2-373d-4705-851e-1b4bc99dae28@nvidia.com> (raw)
In-Reply-To: <dbee61be-4e1c-4f58-ae20-32447b6767fd@kernel.org>
On 01/10/25 22:33, Mario Limonciello wrote:
> External email: Use caution opening links or attachments
>
>
> +linux-doc
>
> On 10/1/25 10:01 AM, Sumit Gupta wrote:
>> Add sysfs interfaces for Minimum Performance, Maximum Performance
>> and Performance Limited Register in the cppc_cpufreq driver.
>>
>> Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
>> Signed-off-by: Sumit Gupta <sumitg@nvidia.com>
>> ---
>> .../ABI/testing/sysfs-devices-system-cpu | 43 +++++++++++++++++++
>> 1 file changed, 43 insertions(+)
>>
>> diff --git a/Documentation/ABI/testing/sysfs-devices-system-cpu
>> b/Documentation/ABI/testing/sysfs-devices-system-cpu
>> index ab8cd337f43a..82141b45d58c 100644
>> --- a/Documentation/ABI/testing/sysfs-devices-system-cpu
>> +++ b/Documentation/ABI/testing/sysfs-devices-system-cpu
>> @@ -327,6 +327,49 @@ Description: Energy performance preference
>>
>> This file is only present if the cppc-cpufreq driver is
>> in use.
>>
>> +What: /sys/devices/system/cpu/cpuX/cpufreq/min_perf
>> +Date: September 2025
>
> These dates will need to push out since this isn't 6.17 material.
Sure.
>
> That being said I have a general question to linux-doc.
>
> Why is this is date based? I would expect a date is meaningless to
> anyone reads this documentation. People who want to know if an
> interface is available would normally look at their kernel version to
> tell.
>
> So wouldn't it make more sense for this field to be something like:
>
> Version: 6.19
>
>> +Contact: linux-pm@vger.kernel.org
>> +Description: Minimum Performance
>> +
>> + Read/write a 32 bits value from/to this file. This file
>> + conveys the minimum performance level at which the
>> platform
>> + may run. Minimum performance may be set to any performance
>> + value in the range [Lowest Performance, Highest
>> Performance],
>
> How will a user discover the lowest -> highest range?
>
> IE I think you should document how to lookup those caps too.
Ok, will add the info about these nodes as below.
Minimum performance may be set to any performance
value in the range [Lowest Performance, Highest Performance],
inclusive but must be set to a value that is less than or
equal to that specified by the Maximum Performance Register.
The range can be checked from nodes:
/sys/devices/system/cpu/cpuX/acpi_cppc/highest_perf
/sys/devices/system/cpu/cpuX/acpi_cppc/lowest_perf
Thank you,
Sumit
>
>> + inclusive but must be set to a value that is less than or
>> + equal to that specified by the Maximum Performance
>> Register.
>> +
>> + Writing to this file only has meaning when Autonomous
>> Selection
>> + is enabled.
>> +
>> + This file is only present if the cppc-cpufreq driver is
>> in use.
>> +
>> +What: /sys/devices/system/cpu/cpuX/cpufreq/max_perf
>> +Date: September 2025
>> +Contact: linux-pm@vger.kernel.org
>> +Description: Minimum Performance
>> +
>> + Read/write a 32 bits value from/to this file. This file
>> conveys
>> + the maximum performance level at which the platform may
>> run.
>> + Maximum performance may be set to any performance value
>> in the
>> + range [Lowest Performance, Highest Performance],
>> inclusive.
>> +
>> + Writing to this file only has meaning when Autonomous
>> Selection is
>> + enabled.
>> +
>> + This file is only present if the cppc-cpufreq driver is
>> in use.
>> +
>> +What: /sys/devices/system/cpu/cpuX/cpufreq/perf_limited
>> +Date: September 2025
>> +Contact: linux-pm@vger.kernel.org
>> +Description: Minimum Performance
>> +
>> + Read/write a 32 bits value from/to this file. This file
>> indicates
>> + to OSPM that an unpredictable event has limited processor
>> + performance, and the delivered performance may be less
>> than
>> + desired/minimum performance.
>> +
>> + This file is only present if the cppc-cpufreq driver is
>> in use.
>>
>> What: /sys/devices/system/cpu/cpu*/cache/index3/cache_disable_{0,1}
>> Date: August 2008
>
next prev parent reply other threads:[~2025-10-08 10:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-01 15:00 [PATCH v3 0/8] Enhanced autonomous selection and improvements Sumit Gupta
2025-10-01 15:00 ` [PATCH v3 1/8] cpufreq: CPPC: Add generic helpers for sysfs show/store Sumit Gupta
2025-10-10 3:24 ` Jie Zhan
2025-10-13 12:51 ` Sumit Gupta
2025-10-01 15:00 ` [PATCH v3 2/8] ACPI: CPPC: Add cppc_get_perf() API to read performance controls Sumit Gupta
2025-10-01 15:00 ` [PATCH v3 3/8] ACPI: CPPC: extend APIs to support auto_sel and epp Sumit Gupta
2025-10-22 9:12 ` Ionela Voinescu
2025-10-24 13:12 ` Sumit Gupta
2025-10-01 15:01 ` [PATCH v3 4/8] ACPI: CPPC: add APIs and sysfs interface for min/max_perf Sumit Gupta
2025-10-22 10:58 ` Ionela Voinescu
2025-10-24 13:22 ` Sumit Gupta
2025-10-01 15:01 ` [PATCH v3 5/8] ACPI: CPPC: add APIs and sysfs interface for perf_limited register Sumit Gupta
2025-10-01 15:01 ` [PATCH v3 6/8] cpufreq: CPPC: Add sysfs for min/max_perf and perf_limited Sumit Gupta
2025-10-01 17:03 ` Mario Limonciello
2025-10-08 10:16 ` Sumit Gupta [this message]
2025-10-10 3:29 ` Jie Zhan
2025-10-13 11:59 ` Sumit Gupta
2025-10-22 12:02 ` Ionela Voinescu
2025-10-24 13:32 ` Sumit Gupta
2025-10-01 15:01 ` [PATCH v3 7/8] cpufreq: CPPC: update policy min/max when toggling auto_select Sumit Gupta
2025-10-01 15:01 ` [PATCH v3 8/8] cpufreq: CPPC: add autonomous mode boot parameter support 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=b7b137d2-373d-4705-851e-1b4bc99dae28@nvidia.com \
--to=sumitg@nvidia.com \
--cc=acpica-devel@lists.linux.dev \
--cc=bbasu@nvidia.com \
--cc=corbet@lwn.net \
--cc=gautham.shenoy@amd.com \
--cc=jonathanh@nvidia.com \
--cc=ksitaraman@nvidia.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=perry.yuan@amd.com \
--cc=pierre.gondois@arm.com \
--cc=rafael@kernel.org \
--cc=ray.huang@amd.com \
--cc=rdunlap@infradead.org \
--cc=robert.moore@intel.com \
--cc=sanjayc@nvidia.com \
--cc=superm1@kernel.org \
--cc=treding@nvidia.com \
--cc=viresh.kumar@linaro.org \
--cc=vsethi@nvidia.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