From: Christian Melendez <chrismelnu@gmail.com>
To: acme@kernel.org
Cc: irogers@google.com, namhyung@kernel.org, jolsa@kernel.org,
peterz@infradead.org, linux-perf-users@vger.kernel.org,
linux-kernel@vger.kernel.org,
Christian Melendez <chrismelnu@gmail.com>
Subject: [PATCH] perf stat: document task-clock/cpu-clock in TIMINGS
Date: Wed, 23 Sep 2026 15:51:40 +0200 [thread overview]
Message-ID: <20260923135140.386033-1-chrismelnu@gmail.com> (raw)
In-Reply-To: <CAP-5=fV0-yvc68BUSKoSajHjHY_A6COgbEJYiFxRg+G-8LeJhQ@mail.gmail.com>
task-clock/cpu-clock appear in perf stat's own example output but
were never explained in perf-stat.txt, unlike time elapsed/user/sys.
This came up unanswered on the list in 2013 and 2015 without docs
ever being added.
Link: https://patch.msgid.link/CAP-5=fV0-yvc68BUSKoSajHjHY_A6COgbEJYiFxRg+G-8LeJhQ@mail.gmail.com
Signed-off-by: Christian Melendez <chrismelnu@gmail.com>
---
tools/perf/Documentation/perf-stat.txt | 12 +++++++++++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/tools/perf/Documentation/perf-stat.txt b/tools/perf/Documentation/perf-stat.txt
index f334aabdc809..c0d6c344f9eb 100644
--- a/tools/perf/Documentation/perf-stat.txt
+++ b/tools/perf/Documentation/perf-stat.txt
@@ -621,6 +621,16 @@ user/system lands:
Those times are the very same as displayed by the 'time' tool.
+We also display a clock-based timing metric that depends on the
+target being monitored:
+
+ 83723.452481 task-clock:u (msec) # 1.004 CPUs utilized
+
+For a single task, task-clock reports a clock count specific to that
+task. When the target is a CPU or the whole system (-a or -C),
+cpu-clock is reported instead. cpu-clock is a high-resolution per-CPU
+timer. See perf_event_open(2) for more details.
+
CSV FORMAT
----------
@@ -671,4 +681,4 @@ that can be used for parsing.
SEE ALSO
--------
-linkperf:perf-top[1], linkperf:perf-list[1]
+linkperf:perf-top[1], linkperf:perf-list[1], perf_event_open(2)
--
2.34.1
next prev parent reply other threads:[~2026-09-23 13:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 21:55 perf stat: worth documenting task-clock/cpu-clock in perf-stat.txt? Christian Melendez
2026-09-23 7:41 ` Ian Rogers
2026-09-23 13:51 ` Christian Melendez [this message]
2026-09-23 15:14 ` [PATCH] perf stat: document task-clock/cpu-clock in TIMINGS Ian Rogers
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=20260923135140.386033-1-chrismelnu@gmail.com \
--to=chrismelnu@gmail.com \
--cc=acme@kernel.org \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®