From: NicoErdmann <nicobsc4@yahoo.com>
To: linux-pm@vger.kernel.org
Cc: linux-doc@vger.kernel.org, rafael@kernel.org,
viresh.kumar@linaro.org, corbet@lwn.net,
skhan@linuxfoundation.org, NicoErdmann <nicobsc4@yahoo.com>
Subject: [PATCH v2] cpufreq-stats: document limitations on modern cpufreq drivers
Date: Sun, 10 May 2026 21:33:52 +0200 [thread overview]
Message-ID: <20260510193352.195181-1-nicobsc4@yahoo.com> (raw)
In-Reply-To: <b23cee4d-dd82-4828-9f38-72cfb05eff32@infradead.org>
Add a note clarifying that cpufreq-stats may not be present or may not provide meaningful statistics depending
on the active CPU frequency scaling driver.
In particular, drivers such as intel_pstate and amd_pstate may use alternative mechanisms for frequency scaling
and accounting.
v2:
- Add missing period at end of sentence (reported by Randy)
Signed-off-by: NicoErdmann <nicobsc4@yahoo.com>
---
Documentation/cpu-freq/cpufreq-stats.rst | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/Documentation/cpu-freq/cpufreq-stats.rst b/Documentation/cpu-freq/cpufreq-stats.rst
index 9ad695b1c7db..6ffa5a6a63c9 100644
--- a/Documentation/cpu-freq/cpufreq-stats.rst
+++ b/Documentation/cpu-freq/cpufreq-stats.rst
@@ -28,6 +28,13 @@ Various statistics will form read_only files under this directory.
This driver is designed to be independent of any particular cpufreq_driver
that may be running on your CPU. So, it will work with any cpufreq_driver.
+.. note::
+
+ On some modern systems, this interface may not be available or may not
+ expose meaningful statistics depending on the active CPU frequency scaling driver.
+
+ In particular, drivers such as intel_pstate or amd_pstate may use alternative
+ mechanisms for frequency scaling and accounting.
2. Statistics Provided (with example)
=====================================
--
2.54.0
prev parent reply other threads:[~2026-05-10 19:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260510143303.120863-1-nicobsc4.ref@yahoo.com>
2026-05-10 14:33 ` [PATCH] cpufreq-stats: document limitations on modern cpufreq drivers NicoErdmann
2026-05-10 17:33 ` Randy Dunlap
2026-05-10 19:33 ` NicoErdmann [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=20260510193352.195181-1-nicobsc4@yahoo.com \
--to=nicobsc4@yahoo.com \
--cc=corbet@lwn.net \
--cc=linux-doc@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