From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Jiri Olsa <jolsa@kernel.org>, Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
linux-perf-users@vger.kernel.org,
Kan Liang <kan.liang@linux.intel.com>,
Leo Yan <leo.yan@linaro.org>
Subject: Re: [PATCH 0/5] perf tools: Clean up cpu map handling for system-wide evsel (v2)
Date: Fri, 30 Sep 2022 16:39:10 -0300 [thread overview]
Message-ID: <YzdF3qfSmQM2Wu+7@kernel.org> (raw)
In-Reply-To: <20220930172714.711616-1-namhyung@kernel.org>
Em Fri, Sep 30, 2022 at 10:27:09AM -0700, Namhyung Kim escreveu:
> Hello,
>
> The system-wide evsel has a cpu map for all (online) cpus regardless
> of user requested cpus. But the cpu map handling code has some
> special case for it and I think we can cleanup the code by making sure
> that such a evsel has a proper cpu/thread maps from the beginning.
> This patches should not cause any change in the behavior.
>
> Changes from v1:
> * use evlist->core.needs_map_propagation field
> * add Reviewed-by from Adrian
Thanks, replaced v1 with this.
Adrian, please check if I can add the Reviewed-by to the ones without
it.
- Arnaldo
> You can get the code from 'perf/cpumap-update-v2' branch in
>
> git://git.kernel.org/pub/scm/linux/kernel/git/namhyung/linux-perf.git
>
> Thanks,
> Namhyung
>
> Namhyung Kim (5):
> libperf: Populate system-wide evsel maps
> libperf: Propagate maps only if necessary
> perf tools: Get rid of evlist__add_on_all_cpus()
> perf tools: Add evlist__add_sched_switch()
> perf tools: Remove special handling of system-wide evsel
>
> tools/lib/perf/evlist.c | 23 ++++++------
> tools/lib/perf/evsel.c | 3 --
> tools/lib/perf/include/internal/evlist.h | 1 +
> tools/perf/arch/x86/util/intel-pt.c | 15 +++-----
> tools/perf/builtin-script.c | 3 --
> tools/perf/tests/switch-tracking.c | 15 +++-----
> tools/perf/util/evlist.c | 46 ++++++++++--------------
> tools/perf/util/evlist.h | 1 +
> tools/perf/util/evsel.c | 12 ++-----
> tools/perf/util/stat.c | 3 --
> 10 files changed, 46 insertions(+), 76 deletions(-)
>
>
> base-commit: 62e64c9d2fd12839c02f1b3e8b873e7cb34e8720
> --
> 2.38.0.rc1.362.ged0d419d3c-goog
--
- Arnaldo
prev parent reply other threads:[~2022-09-30 19:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 17:27 [PATCH 0/5] perf tools: Clean up cpu map handling for system-wide evsel (v2) Namhyung Kim
2022-09-30 17:27 ` [PATCH 1/5] libperf: Populate system-wide evsel maps Namhyung Kim
2022-09-30 17:27 ` [PATCH 2/5] libperf: Propagate maps only if necessary Namhyung Kim
2022-10-03 5:36 ` Adrian Hunter
2022-10-04 5:20 ` Adrian Hunter
2022-09-30 17:27 ` [PATCH 3/5] perf tools: Get rid of evlist__add_on_all_cpus() Namhyung Kim
2022-09-30 17:27 ` [PATCH 4/5] perf tools: Add evlist__add_sched_switch() Namhyung Kim
2022-09-30 17:27 ` [PATCH 5/5] perf tools: Remove special handling of system-wide evsel Namhyung Kim
2022-09-30 19:39 ` Arnaldo Carvalho de Melo [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=YzdF3qfSmQM2Wu+7@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=leo.yan@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@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 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.