From: Namhyung Kim <namhyung@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
James Clark <james.clark@linaro.org>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH] perf stat: Add ScaleUnit to {cpu,task}-clock JSON description
Date: Fri, 7 Nov 2025 09:53:27 -0800 [thread overview]
Message-ID: <aQ4yF-_bDedF2535@google.com> (raw)
In-Reply-To: <CAP-5=fU6gyWb25Qd=U3wZiQ_6D72qVXPKvo6XKQpAu03tAPVUg@mail.gmail.com>
On Thu, Nov 06, 2025 at 02:09:00PM -0800, Ian Rogers wrote:
> On Thu, Nov 6, 2025 at 1:53 PM Namhyung Kim <namhyung@kernel.org> wrote:
> >
> > This changes the output of the event like below. In fact, that's the
> > output it used to have before the JSON conversion.
> >
> > Before:
> > $ perf stat -e task-clock true
> >
> > Performance counter stats for 'true':
> >
> > 313,848 task-clock # 0.290 CPUs utilized
> >
> > 0.001081223 seconds time elapsed
> >
> > 0.001122000 seconds user
> > 0.000000000 seconds sys
> >
> > After:
> > $ perf stat -e task-clock true
> >
> > Performance counter stats for 'true':
> >
> > 0.36 msec task-clock # 0.297 CPUs utilized
> >
> > 0.001225435 seconds time elapsed
> >
> > 0.001268000 seconds user
> > 0.000000000 seconds sys
> >
> > Fixes: 9957d8c801fe0cb90 ("perf jevents: Add common software event json")
> > Signed-off-by: Namhyung Kim <namhyung@kernel.org>
>
> Reviewed-by: Ian Rogers <irogers@google.com>
Applied to perf-tools-next, thanks!
Namhyung
prev parent reply other threads:[~2025-11-07 17:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 21:53 [PATCH] perf stat: Add ScaleUnit to {cpu,task}-clock JSON description Namhyung Kim
2025-11-06 22:09 ` Ian Rogers
2025-11-07 17:53 ` Namhyung Kim [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=aQ4yF-_bDedF2535@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@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