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,
Andi Kleen <ak@linux.intel.com>,
Dapeng Mi <dapeng1.mi@linux.intel.com>
Subject: Re: [PATCH v4 09/10] perf stat: Read tool events last
Date: Mon, 17 Nov 2025 22:46:51 -0800 [thread overview]
Message-ID: <aRwWWz3kNc5AkwX9@google.com> (raw)
In-Reply-To: <CAP-5=fVidOjNDZCX6Ain83KFp0Zk8aHTJX7_KgwfTY885DuPKg@mail.gmail.com>
On Mon, Nov 17, 2025 at 08:38:15PM -0800, Ian Rogers wrote:
> On Mon, Nov 17, 2025 at 6:35 PM Namhyung Kim <namhyung@kernel.org> wrote:
> >
> > On Thu, Nov 13, 2025 at 10:05:15AM -0800, Ian Rogers wrote:
> > > When reading a metric like memory bandwidth on multiple sockets, the
> > > additional sockets will be on CPUS > 0. Because of the affinity
> > > reading, the counters are read on CPU 0 along with the time, then the
> > > later sockets are read. This can lead to the later sockets having a
> > > bandwidth larger than is possible for the period of time. To avoid
> > > this moving the reading of tool events to occur after all other events
> > > are read.
> >
> > Can you move this change before the affinity updates? I think it's
> > straight-forward and can be applied independently.
>
> It is straightforward but will require changes to
> read_counters_with_affinity. I can do a v5 once I know what to do with
> the other patches.
I plan to merge patch 1 to 7 first. And I think it'd good to have this
one as well.
Thanks,
Namhyung
> >
> > >
> > > Signed-off-by: Ian Rogers <irogers@google.com>
> > > ---
> > > tools/perf/builtin-stat.c | 29 ++++++++++++++++++++++++++++-
> > > tools/perf/util/evlist.c | 4 ----
> > > 2 files changed, 28 insertions(+), 5 deletions(-)
> > >
> > > diff --git a/tools/perf/builtin-stat.c b/tools/perf/builtin-stat.c
> > > index 947f11b8b106..aec93b91fd11 100644
> > > --- a/tools/perf/builtin-stat.c
> > > +++ b/tools/perf/builtin-stat.c
> > > @@ -379,6 +379,9 @@ static int read_counters_with_affinity(void)
> > > if (evsel__is_bpf(counter))
> > > continue;
> > >
> > > + if (evsel__is_tool(counter))
> > > + continue;
> > > +
> > > if (!counter->err)
> > > counter->err = read_counter_cpu(counter, evlist_cpu_itr.cpu_map_idx);
> > > }
> > > @@ -402,6 +405,24 @@ static int read_bpf_map_counters(void)
> > > return 0;
> > > }
> > >
> > > +static int read_tool_counters(void)
> > > +{
> > > + struct evsel *counter;
> > > +
> > > + evlist__for_each_entry(evsel_list, counter) {
> > > + int idx;
> > > +
> > > + if (!evsel__is_tool(counter))
> > > + continue;
> > > +
> > > + perf_cpu_map__for_each_idx(idx, counter->core.cpus) {
> > > + if (!counter->err)
> > > + counter->err = read_counter_cpu(counter, idx);
> > > + }
> > > + }
> > > + return 0;
> > > +}
> > > +
> > > static int read_counters(void)
> > > {
> > > int ret;
> > > @@ -415,7 +436,13 @@ static int read_counters(void)
> > > return ret;
> > >
> > > // Read non-BPF and non-tool counters next.
> > > - return read_counters_with_affinity();
> > > + ret = read_counters_with_affinity();
> > > + if (ret)
> > > + return ret;
> > > +
> > > + // Read the tool counters last. This way the duration_time counter
> > > + // should always be greater than any other counter's enabled time.
> > > + return read_tool_counters();
> > > }
> > >
> > > static void process_counters(void)
> > > diff --git a/tools/perf/util/evlist.c b/tools/perf/util/evlist.c
> > > index b6df81b8a236..fc3dae7cdfca 100644
> > > --- a/tools/perf/util/evlist.c
> > > +++ b/tools/perf/util/evlist.c
> > > @@ -368,10 +368,6 @@ static bool evlist__use_affinity(struct evlist *evlist)
> > > struct perf_cpu_map *used_cpus = NULL;
> > > bool ret = false;
> > >
> > > - /*
> > > - * With perf record core.user_requested_cpus is usually NULL.
> > > - * Use the old method to handle this for now.
> > > - */
> > > if (!evlist->core.user_requested_cpus ||
> > > cpu_map__is_dummy(evlist->core.user_requested_cpus))
> > > return false;
> > > --
> > > 2.51.2.1041.gc1ab5b90ca-goog
> > >
next prev parent reply other threads:[~2025-11-18 6:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 18:05 [PATCH v4 00/10] perf stat fixes and improvements Ian Rogers
2025-11-13 18:05 ` [PATCH v4 01/10] libperf cpumap: Reduce allocations and sorting in intersect Ian Rogers
2025-11-13 18:05 ` [PATCH v4 02/10] perf pmu: perf_cpu_map__new_int to avoid parsing a string Ian Rogers
2025-11-13 18:05 ` [PATCH v4 03/10] perf tool_pmu: Use old_count when computing count values for time events Ian Rogers
2025-11-13 18:05 ` [PATCH v4 04/10] perf stat-shadow: Read tool events directly Ian Rogers
2025-11-18 2:30 ` Namhyung Kim
2025-11-18 4:36 ` Ian Rogers
2025-11-18 6:45 ` Namhyung Kim
2025-11-13 18:05 ` [PATCH v4 05/10] perf stat: Reduce scope of ru_stats Ian Rogers
2025-11-18 2:31 ` Namhyung Kim
2025-11-13 18:05 ` [PATCH v4 06/10] perf stat: Reduce scope of walltime_nsecs_stats Ian Rogers
2025-11-13 18:05 ` [PATCH v4 07/10] perf tool_pmu: More accurately set the cpus for tool events Ian Rogers
2025-11-13 18:05 ` [PATCH v4 08/10] perf evlist: Reduce affinity use and move into iterator, fix no affinity Ian Rogers
2025-11-13 18:05 ` [PATCH v4 09/10] perf stat: Read tool events last Ian Rogers
2025-11-18 2:35 ` Namhyung Kim
2025-11-18 4:38 ` Ian Rogers
2025-11-18 6:46 ` Namhyung Kim [this message]
2025-11-13 18:05 ` [PATCH v4 10/10] perf stat: Add no-affinity flag Ian Rogers
2025-11-18 2:40 ` Namhyung Kim
2025-11-18 4:32 ` Ian Rogers
2025-11-18 6:50 ` Namhyung Kim
2025-11-18 18:00 ` [PATCH v4 00/10] perf stat fixes and improvements Namhyung Kim
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=aRwWWz3kNc5AkwX9@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=dapeng1.mi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).