From: Jiri Olsa <jolsa@redhat.com>
To: James Clark <james.clark@arm.com>
Cc: linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
namhyung@kernel.org, john.garry@huawei.com
Subject: Re: [PATCH v6 00/12] perf tools: fix perf stat with large socket IDs
Date: Thu, 3 Dec 2020 16:39:23 +0100 [thread overview]
Message-ID: <20201203153923.GA3613481@krava> (raw)
In-Reply-To: <20201126141328.6509-1-james.clark@arm.com>
On Thu, Nov 26, 2020 at 04:13:16PM +0200, James Clark wrote:
> Changes since v5:
> * Fix test for cpu_map__get_die() by shifting id before testing.
> * Fix test for cpu_map__get_socket() by not using cpu_map__id_to_socket()
> which is only valid in CPU aggregation mode.
>
> 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
Acked-by: Jiri Olsa <jolsa@redhat.com>
thanks,
jirka
>
> tools/perf/builtin-stat.c | 128 ++++++++++++------------
> tools/perf/tests/topology.c | 64 ++++++++++--
> 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, 337 insertions(+), 194 deletions(-)
>
> --
> 2.28.0
>
next prev parent reply other threads:[~2020-12-03 15:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 14:13 [PATCH v6 00/12] perf tools: fix perf stat with large socket IDs James Clark
2020-11-26 14:13 ` [PATCH v6 01/12] perf tools: Improve topology test James Clark
2020-11-26 14:13 ` [PATCH v6 02/12] perf tools: Use allocator for perf_cpu_map James Clark
2020-11-26 14:13 ` [PATCH v6 03/12] perf tools: Add new struct for cpu aggregation James Clark
2020-11-26 14:13 ` [PATCH v6 04/12] perf tools: Replace aggregation ID with a struct James Clark
2020-11-26 14:13 ` [PATCH v6 05/12] perf tools: add new map type for aggregation James Clark
2020-11-26 14:13 ` [PATCH v6 06/12] perf tools: drop in cpu_aggr_map struct James Clark
2020-11-26 14:13 ` [PATCH v6 07/12] perf tools: Start using cpu_aggr_id in map James Clark
2020-11-26 14:13 ` [PATCH v6 08/12] perf tools: Add separate node member James Clark
2020-11-26 14:13 ` [PATCH v6 09/12] perf tools: Add separate socket member James Clark
2020-11-26 14:13 ` [PATCH v6 10/12] perf tools: Add separate die member James Clark
2020-11-26 14:13 ` [PATCH v6 11/12] perf tools: Add separate core member James Clark
2020-11-26 14:13 ` [PATCH v6 12/12] perf tools: Add separate thread member James Clark
2020-11-30 14:33 ` [PATCH v6 00/12] perf tools: fix perf stat with large socket IDs Namhyung Kim
2020-12-03 15:39 ` Jiri Olsa [this message]
2020-12-04 11:48 ` John Garry
2020-12-04 11:48 ` John Garry
2020-12-23 22:17 ` Jiri Olsa
2020-12-23 22:17 ` Jiri Olsa
2020-12-24 12:30 ` Arnaldo Carvalho de Melo
2020-12-24 12:30 ` 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=20201203153923.GA3613481@krava \
--to=jolsa@redhat.com \
--cc=james.clark@arm.com \
--cc=john.garry@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@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 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.