From: Namhyung Kim <namhyung@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
"Dr. David Alan Gilbert" <linux@treblig.org>,
Yang Li <yang.lee@linux.alibaba.com>,
James Clark <james.clark@linaro.org>,
Thomas Falcon <thomas.falcon@intel.com>,
Thomas Richter <tmricht@linux.ibm.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 2/3] perf stat-shadow: Read tool events directly
Date: Tue, 4 Nov 2025 10:10:32 -0800 [thread overview]
Message-ID: <aQpBmIEX8G7mTrWQ@google.com> (raw)
In-Reply-To: <20251104053449.1208800-2-irogers@google.com>
Hi Ian,
On Mon, Nov 03, 2025 at 09:34:48PM -0800, Ian Rogers wrote:
> When reading time values for metrics don't use the globals updated in
> builtin-stat, just read the events as regular events. The only
> exception is for time events where nanoseconds need converting to
> seconds as metrics assume time metrics are in seconds.
>
> Signed-off-by: Ian Rogers <irogers@google.com>
> ---
> tools/perf/util/stat-shadow.c | 123 +++++++++++++---------------------
> 1 file changed, 45 insertions(+), 78 deletions(-)
>
> diff --git a/tools/perf/util/stat-shadow.c b/tools/perf/util/stat-shadow.c
> index abaf6b579bfc..9fae3d32a519 100644
> --- a/tools/perf/util/stat-shadow.c
> +++ b/tools/perf/util/stat-shadow.c
> @@ -371,6 +371,18 @@ static void print_nsecs(struct perf_stat_config *config,
> }
> }
>
> +static double tool_pmu__scale_for_metric(const struct evsel *evsel)
> +{
> + enum tool_pmu_event event = evsel__tool_event(evsel);
> +
> + if (event == TOOL_PMU__EVENT_DURATION_TIME ||
> + event == TOOL_PMU__EVENT_USER_TIME ||
> + event == TOOL_PMU__EVENT_SYSTEM_TIME)
> + return 1e-9; /* Scale nanoseconds to seconds. */
> +
> + return 1.0;
> +}
> +
> static int prepare_metric(const struct metric_expr *mexp,
> const struct evsel *evsel,
> struct expr_parse_ctx *pctx,
> @@ -382,90 +394,45 @@ static int prepare_metric(const struct metric_expr *mexp,
>
> for (i = 0; metric_events[i]; i++) {
> char *n;
> - double val;
> + double val, scale = tool_pmu__scale_for_metric(metric_events[i]);
> int source_count = 0;
> + struct perf_stat_evsel *ps = metric_events[i]->stats;
> + struct perf_stat_aggr *aggr;
>
> - if (evsel__is_tool(metric_events[i])) {
> - struct stats *stats;
> - double scale;
> -
> - switch (evsel__tool_event(metric_events[i])) {
> - case TOOL_PMU__EVENT_DURATION_TIME:
> - stats = &walltime_nsecs_stats;
> - scale = 1e-9;
> - break;
> - case TOOL_PMU__EVENT_USER_TIME:
> - stats = &ru_stats.ru_utime_usec_stat;
> - scale = 1e-6;
> - break;
> - case TOOL_PMU__EVENT_SYSTEM_TIME:
> - stats = &ru_stats.ru_stime_usec_stat;
> - scale = 1e-6;
Do {USER,SYSTEM}_TIME become nanosecond now?
Thanks,
Namhyung
> + /*
> + * If there are multiple uncore PMUs and we're not reading the
> + * leader's stats, determine the stats for the appropriate
> + * uncore PMU.
> + */
> + if (evsel && evsel->metric_leader &&
> + evsel->pmu != evsel->metric_leader->pmu &&
> + mexp->metric_events[i]->pmu == evsel->metric_leader->pmu) {
> + struct evsel *pos;
> +
> + evlist__for_each_entry(evsel->evlist, pos) {
> + if (pos->pmu != evsel->pmu)
> + continue;
> + if (pos->metric_leader != mexp->metric_events[i])
> + continue;
> + ps = pos->stats;
> + source_count = 1;
> break;
> - case TOOL_PMU__EVENT_NONE:
> - pr_err("Invalid tool event 'none'");
> - abort();
> - case TOOL_PMU__EVENT_MAX:
> - pr_err("Invalid tool event 'max'");
> - abort();
> - case TOOL_PMU__EVENT_HAS_PMEM:
> - case TOOL_PMU__EVENT_NUM_CORES:
> - case TOOL_PMU__EVENT_NUM_CPUS:
> - case TOOL_PMU__EVENT_NUM_CPUS_ONLINE:
> - case TOOL_PMU__EVENT_NUM_DIES:
> - case TOOL_PMU__EVENT_NUM_PACKAGES:
> - case TOOL_PMU__EVENT_SLOTS:
> - case TOOL_PMU__EVENT_SMT_ON:
> - case TOOL_PMU__EVENT_SYSTEM_TSC_FREQ:
> - default:
> - pr_err("Unexpected tool event '%s'", evsel__name(metric_events[i]));
> - abort();
> }
> - val = avg_stats(stats) * scale;
> - source_count = 1;
> - } else {
> - struct perf_stat_evsel *ps = metric_events[i]->stats;
> - struct perf_stat_aggr *aggr;
> -
> + }
> + aggr = &ps->aggr[aggr_idx];
> + if (!aggr || !metric_events[i]->supported) {
> /*
> - * If there are multiple uncore PMUs and we're not
> - * reading the leader's stats, determine the stats for
> - * the appropriate uncore PMU.
> + * Not supported events will have a count of 0, which
> + * can be confusing in a metric. Explicitly set the
> + * value to NAN. Not counted events (enable time of 0)
> + * are read as 0.
> */
> - if (evsel && evsel->metric_leader &&
> - evsel->pmu != evsel->metric_leader->pmu &&
> - mexp->metric_events[i]->pmu == evsel->metric_leader->pmu) {
> - struct evsel *pos;
> -
> - evlist__for_each_entry(evsel->evlist, pos) {
> - if (pos->pmu != evsel->pmu)
> - continue;
> - if (pos->metric_leader != mexp->metric_events[i])
> - continue;
> - ps = pos->stats;
> - source_count = 1;
> - break;
> - }
> - }
> - aggr = &ps->aggr[aggr_idx];
> - if (!aggr)
> - break;
> -
> - if (!metric_events[i]->supported) {
> - /*
> - * Not supported events will have a count of 0,
> - * which can be confusing in a
> - * metric. Explicitly set the value to NAN. Not
> - * counted events (enable time of 0) are read as
> - * 0.
> - */
> - val = NAN;
> - source_count = 0;
> - } else {
> - val = aggr->counts.val;
> - if (!source_count)
> - source_count = evsel__source_count(metric_events[i]);
> - }
> + val = NAN;
> + source_count = 0;
> + } else {
> + val = aggr->counts.val * scale;
> + if (!source_count)
> + source_count = evsel__source_count(metric_events[i]);
> }
> n = strdup(evsel__metric_id(metric_events[i]));
> if (!n)
> --
> 2.51.2.1006.ga50a493c49-goog
>
next prev parent reply other threads:[~2025-11-04 18:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 5:34 [PATCH v1 1/3] perf tool_pmu: Use old_count when computing count values for time events Ian Rogers
2025-11-04 5:34 ` [PATCH v1 2/3] perf stat-shadow: Read tool events directly Ian Rogers
2025-11-04 18:10 ` Namhyung Kim [this message]
2025-11-04 18:47 ` Ian Rogers
2025-11-04 5:34 ` [PATCH v1 3/3] perf stat: Reduce scope of ru_stats 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=aQpBmIEX8G7mTrWQ@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.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=linux@treblig.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=thomas.falcon@intel.com \
--cc=tmricht@linux.ibm.com \
--cc=yang.lee@linux.alibaba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.