From: Jiri Olsa <jolsa@redhat.com>
To: kan.liang@linux.intel.com
Cc: acme@kernel.org, jolsa@kernel.org, mingo@redhat.com,
linux-kernel@vger.kernel.org, peterz@infradead.org,
ak@linux.intel.com
Subject: Re: [PATCH V3 1/5] perf cpumap: Retrieve die id information
Date: Wed, 5 Jun 2019 11:09:07 +0200 [thread overview]
Message-ID: <20190605090907.GC23116@krava> (raw)
In-Reply-To: <1559688644-106558-1-git-send-email-kan.liang@linux.intel.com>
On Tue, Jun 04, 2019 at 03:50:40PM -0700, kan.liang@linux.intel.com wrote:
> From: Kan Liang <kan.liang@linux.intel.com>
>
> There is no function to retrieve die id information of a given CPU.
>
> Add cpu_map__get_die_id() to retrieve die id information.
>
> Signed-off-by: Kan Liang <kan.liang@linux.intel.com>
> ---
>
> No changes since V2.
Reviewed-by: Jiri Olsa <jolsa@kernel.org>
for the whole patchset
thanks,
jirka
>
> tools/perf/util/cpumap.c | 7 +++++++
> tools/perf/util/cpumap.h | 1 +
> 2 files changed, 8 insertions(+)
>
> diff --git a/tools/perf/util/cpumap.c b/tools/perf/util/cpumap.c
> index 0b59922..7db1365 100644
> --- a/tools/perf/util/cpumap.c
> +++ b/tools/perf/util/cpumap.c
> @@ -373,6 +373,13 @@ int cpu_map__build_map(struct cpu_map *cpus, struct cpu_map **res,
> return 0;
> }
>
> +int cpu_map__get_die_id(int cpu)
> +{
> + int value, ret = cpu__get_topology_int(cpu, "die_id", &value);
> +
> + return ret ?: value;
> +}
> +
> int cpu_map__get_core_id(int cpu)
> {
> int value, ret = cpu__get_topology_int(cpu, "core_id", &value);
> diff --git a/tools/perf/util/cpumap.h b/tools/perf/util/cpumap.h
> index f00ce62..6762ff9 100644
> --- a/tools/perf/util/cpumap.h
> +++ b/tools/perf/util/cpumap.h
> @@ -25,6 +25,7 @@ size_t cpu_map__snprint_mask(struct cpu_map *map, char *buf, size_t size);
> size_t cpu_map__fprintf(struct cpu_map *map, FILE *fp);
> int cpu_map__get_socket_id(int cpu);
> int cpu_map__get_socket(struct cpu_map *map, int idx, void *data);
> +int cpu_map__get_die_id(int cpu);
> int cpu_map__get_core_id(int cpu);
> int cpu_map__get_core(struct cpu_map *map, int idx, void *data);
> int cpu_map__build_socket_map(struct cpu_map *cpus, struct cpu_map **sockp);
> --
> 2.7.4
>
next prev parent reply other threads:[~2019-06-05 9:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 22:50 [PATCH V3 1/5] perf cpumap: Retrieve die id information kan.liang
2019-06-04 22:50 ` [PATCH V3 2/5] perf header: Add die information in CPU topology kan.liang
2019-06-06 19:12 ` Arnaldo Carvalho de Melo
2019-06-06 20:08 ` Arnaldo Carvalho de Melo
2019-06-06 20:56 ` Liang, Kan
2019-06-17 19:32 ` [tip:perf/core] " tip-bot for Kan Liang
2019-06-04 22:50 ` [PATCH V3 3/5] perf stat: Support per-die aggregation kan.liang
2019-06-04 22:50 ` [PATCH V3 4/5] perf header: Rename "sibling cores" to "sibling sockets" kan.liang
2019-06-17 19:34 ` [tip:perf/core] " tip-bot for Kan Liang
2019-06-04 22:50 ` [PATCH V3 5/5] perf tools: Apply new CPU topology sysfs attributes kan.liang
2019-06-17 19:34 ` [tip:perf/core] " tip-bot for Kan Liang
2019-06-05 9:09 ` Jiri Olsa [this message]
2019-06-06 19:19 ` [PATCH V3 1/5] perf cpumap: Retrieve die id information Arnaldo Carvalho de Melo
2019-06-17 19:32 ` [tip:perf/core] " tip-bot for Kan Liang
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=20190605090907.GC23116@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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.