From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Namhyung Kim <namhyung@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] perf evlist: Avoid iteration for empty evlist.
Date: Fri, 18 Mar 2022 11:26:55 -0300 [thread overview]
Message-ID: <YjSWr5P6J1fN2PiR@kernel.org> (raw)
In-Reply-To: <20220317231643.550902-1-irogers@google.com>
Em Thu, Mar 17, 2022 at 04:16:43PM -0700, Ian Rogers escreveu:
> As seen with 'perf stat --null ..' and reported in:
> https://lore.kernel.org/lkml/YjCLcpcX2peeQVCH@kernel.org/
>
> v2. Avoids setting evsel in the empty list case as suggested by Jiri
> Olsa <jolsa@kernel.org>.
> Fixes: 472832d2c000 ("perf evlist: Refactor evlist__for_each_cpu()")
> Signed-off-by: Ian Rogers <irogers@google.com>
Thanks, replaced v1 with this new one.
- Arnaldo
> ---
> tools/perf/util/evlist.c | 28 +++++++++++++++++-----------
> 1 file changed, 17 insertions(+), 11 deletions(-)
>
> diff --git a/tools/perf/util/evlist.c b/tools/perf/util/evlist.c
> index 8134d45e2164..9bb79e049957 100644
> --- a/tools/perf/util/evlist.c
> +++ b/tools/perf/util/evlist.c
> @@ -346,7 +346,7 @@ struct evlist_cpu_iterator evlist__cpu_begin(struct evlist *evlist, struct affin
> {
> struct evlist_cpu_iterator itr = {
> .container = evlist,
> - .evsel = evlist__first(evlist),
> + .evsel = NULL,
> .cpu_map_idx = 0,
> .evlist_cpu_map_idx = 0,
> .evlist_cpu_map_nr = perf_cpu_map__nr(evlist->core.all_cpus),
> @@ -354,16 +354,22 @@ struct evlist_cpu_iterator evlist__cpu_begin(struct evlist *evlist, struct affin
> .affinity = affinity,
> };
>
> - if (itr.affinity) {
> - itr.cpu = perf_cpu_map__cpu(evlist->core.all_cpus, 0);
> - affinity__set(itr.affinity, itr.cpu.cpu);
> - itr.cpu_map_idx = perf_cpu_map__idx(itr.evsel->core.cpus, itr.cpu);
> - /*
> - * If this CPU isn't in the evsel's cpu map then advance through
> - * the list.
> - */
> - if (itr.cpu_map_idx == -1)
> - evlist_cpu_iterator__next(&itr);
> + if (evlist__empty(evlist)) {
> + /* Ensure the empty list doesn't iterate. */
> + itr.evlist_cpu_map_idx = itr.evlist_cpu_map_nr;
> + } else {
> + itr.evsel = evlist__first(evlist);
> + if (itr.affinity) {
> + itr.cpu = perf_cpu_map__cpu(evlist->core.all_cpus, 0);
> + affinity__set(itr.affinity, itr.cpu.cpu);
> + itr.cpu_map_idx = perf_cpu_map__idx(itr.evsel->core.cpus, itr.cpu);
> + /*
> + * If this CPU isn't in the evsel's cpu map then advance
> + * through the list.
> + */
> + if (itr.cpu_map_idx == -1)
> + evlist_cpu_iterator__next(&itr);
> + }
> }
> return itr;
> }
> --
> 2.35.1.894.gb6a874cedc-goog
--
- Arnaldo
next prev parent reply other threads:[~2022-03-18 14:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 23:16 [PATCH v2] perf evlist: Avoid iteration for empty evlist Ian Rogers
2022-03-18 14:26 ` Arnaldo Carvalho de Melo [this message]
2022-03-18 20:40 ` Jiri Olsa
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=YjSWr5P6J1fN2PiR@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.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