From: James Clark <james.clark@arm.com>
To: linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
jolsa@redhat.com
Cc: james.clark@arm.com
Subject: [PATCH v5 00/12] perf tools: fix perf stat with large socket IDs
Date: Tue, 17 Nov 2020 16:48:33 +0200 [thread overview]
Message-ID: <20201117144845.13714-1-james.clark@arm.com> (raw)
Changes since v4:
* Test all fields in topology test, even if they should be -1
* Remove extra refcount from cpu_map__build_map()
* Reduce the changes in sort_aggr_thread()
* Move addition of cpu_aggr_map__put() and cpu_aggr_map__delete()
into the commit where they are used so that they don't have
to be changed to static in a separate commit
James Clark (12):
perf tools: Improve topology test
perf tools: Use allocator for perf_cpu_map
perf tools: Add new struct for cpu aggregation
perf tools: Replace aggregation ID with a struct
perf tools: add new map type for aggregation
perf tools: drop in cpu_aggr_map struct
perf tools: Start using cpu_aggr_id in map
perf tools: Add separate node member
perf tools: Add separate socket member
perf tools: Add separate die member
perf tools: Add separate core member
perf tools: Add separate thread member
tools/perf/builtin-stat.c | 128 ++++++++++++------------
tools/perf/tests/topology.c | 62 ++++++++++--
tools/perf/util/cpumap.c | 171 ++++++++++++++++++++++-----------
tools/perf/util/cpumap.h | 55 ++++++-----
tools/perf/util/stat-display.c | 102 ++++++++++++--------
tools/perf/util/stat.c | 2 +-
tools/perf/util/stat.h | 9 +-
7 files changed, 335 insertions(+), 194 deletions(-)
--
2.28.0
next reply other threads:[~2020-11-17 14:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 14:48 James Clark [this message]
2020-11-17 14:48 ` [PATCH v5 01/12] perf tools: Improve topology test James Clark
2020-11-18 11:21 ` Namhyung Kim
2020-11-26 13:46 ` James Clark
2020-11-17 14:48 ` [PATCH v5 02/12] perf tools: Use allocator for perf_cpu_map James Clark
2020-11-17 14:48 ` [PATCH v5 03/12] perf tools: Add new struct for cpu aggregation James Clark
2020-11-17 14:48 ` [PATCH v5 04/12] perf tools: Replace aggregation ID with a struct James Clark
2020-11-17 14:48 ` [PATCH v5 05/12] perf tools: add new map type for aggregation James Clark
2020-11-17 14:48 ` [PATCH v5 06/12] perf tools: drop in cpu_aggr_map struct James Clark
2020-11-17 14:48 ` [PATCH v5 07/12] perf tools: Start using cpu_aggr_id in map James Clark
2020-11-17 14:48 ` [PATCH v5 08/12] perf tools: Add separate node member James Clark
2020-11-17 14:48 ` [PATCH v5 09/12] perf tools: Add separate socket member James Clark
2020-11-17 14:48 ` [PATCH v5 10/12] perf tools: Add separate die member James Clark
2020-11-17 14:48 ` [PATCH v5 11/12] perf tools: Add separate core member James Clark
2020-11-17 14:48 ` [PATCH v5 12/12] perf tools: Add separate thread member James Clark
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=20201117144845.13714-1-james.clark@arm.com \
--to=james.clark@arm.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.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;
as well as URLs for NNTP newsgroup(s).