From: James Clark <james.clark@linaro.org>
To: Ian Rogers <irogers@google.com>
Cc: Stephane Eranian <eranian@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
Thomas Richter <tmricht@linux.ibm.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] perf tool_pmu: Fix aggregation on duration_time
Date: Wed, 23 Apr 2025 09:58:38 +0100 [thread overview]
Message-ID: <b05aa0fc-05ab-4784-90ab-2d91b78d152b@linaro.org> (raw)
In-Reply-To: <20250423050358.94310-1-irogers@google.com>
On 23/04/2025 6:03 am, Ian Rogers wrote:
> evsel__count_has_error fails counters when the enabled or running time
> are 0. The duration_time event reads 0 when the cpu_map_idx != 0 to
> avoid aggregating time over CPUs. Change the enable and running time
> to always have a ratio of 100% so that evsel__count_has_error won't
> fail.
>
> Before:
> ```
> $ sudo /tmp/perf/perf stat --per-core -a -M UNCORE_FREQ sleep 1
>
> Performance counter stats for 'system wide':
>
> S0-D0-C0 1 2,615,819,485 UNC_CLOCK.SOCKET # 2.61 UNCORE_FREQ
> S0-D0-C0 2 <not counted> duration_time
>
> 1.002111784 seconds time elapsed
> ```
>
> After:
> ```
> $ perf stat --per-core -a -M UNCORE_FREQ sleep 1
>
> Performance counter stats for 'system wide':
>
> S0-D0-C0 1 758,160,296 UNC_CLOCK.SOCKET # 0.76 UNCORE_FREQ
> S0-D0-C0 2 1,003,438,246 duration_time
>
> 1.002486017 seconds time elapsed
> ```
>
> Note: the metric reads the value a different way and isn't impacted.
>
> Reported-by: Stephane Eranian <eranian@google.com>
> Fixes: 240505b2d0ad ("perf tool_pmu: Factor tool events into their own PMU")
> Signed-off-by: Ian Rogers <irogers@google.com>
> ---
> tools/perf/util/tool_pmu.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/tools/perf/util/tool_pmu.c b/tools/perf/util/tool_pmu.c
> index 97b327d1ce4a..727a10e3f990 100644
> --- a/tools/perf/util/tool_pmu.c
> +++ b/tools/perf/util/tool_pmu.c
> @@ -486,8 +486,14 @@ int evsel__tool_pmu_read(struct evsel *evsel, int cpu_map_idx, int thread)
> delta_start *= 1000000000 / ticks_per_sec;
> }
> count->val = delta_start;
> - count->ena = count->run = delta_start;
> count->lost = 0;
> + /*
> + * The values of enabled and running must make a ratio of 100%. The
> + * exact values don't matter as long as they are non-zero to avoid
> + * issues with evsel__count_has_error.
> + */
> + count->ena++;
> + count->run++;
> return 0;
> }
>
Reviewed-by: James Clark <james.clark@linaro.org>
next prev parent reply other threads:[~2025-04-23 8:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 5:03 [PATCH v1] perf tool_pmu: Fix aggregation on duration_time Ian Rogers
2025-04-23 8:58 ` James Clark [this message]
2025-04-24 12:57 ` Arnaldo Carvalho de Melo
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=b05aa0fc-05ab-4784-90ab-2d91b78d152b@linaro.org \
--to=james.clark@linaro.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=tmricht@linux.ibm.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.