From: "Jin, Yao" <yao.jin@linux.intel.com>
To: acme@kernel.org, jolsa@kernel.org, peterz@infradead.org,
mingo@redhat.com, alexander.shishkin@linux.intel.com
Cc: Linux-kernel@vger.kernel.org, ak@linux.intel.com,
kan.liang@intel.com, yao.jin@intel.com
Subject: Re: [PATCH v2 1/3] libperf: Add perf_cpu_map__default_new()
Date: Wed, 30 Jun 2021 20:35:23 +0800 [thread overview]
Message-ID: <858b4c6f-99dd-c0d8-d8ec-67f905b3287c@linux.intel.com> (raw)
In-Reply-To: <20210621143321.27451-1-yao.jin@linux.intel.com>
Hi Arnaldo,
Any comments for v2 series of cpulist hybrid support? :)
Thanks
Jin Yao
On 6/21/2021 10:33 PM, Jin Yao wrote:
> The libperf already has a static function 'cpu_map__default_new()'.
> Add a new API perf_cpu_map__default_new() to export the function.
>
> Signed-off-by: Jin Yao <yao.jin@linux.intel.com>
> ---
> tools/lib/perf/cpumap.c | 5 +++++
> tools/lib/perf/include/perf/cpumap.h | 1 +
> 2 files changed, 6 insertions(+)
>
> diff --git a/tools/lib/perf/cpumap.c b/tools/lib/perf/cpumap.c
> index ca0215047c32..51b6553912e0 100644
> --- a/tools/lib/perf/cpumap.c
> +++ b/tools/lib/perf/cpumap.c
> @@ -68,6 +68,11 @@ static struct perf_cpu_map *cpu_map__default_new(void)
> return cpus;
> }
>
> +struct perf_cpu_map *perf_cpu_map__default_new(void)
> +{
> + return cpu_map__default_new();
> +}
> +
> static int cmp_int(const void *a, const void *b)
> {
> return *(const int *)a - *(const int*)b;
> diff --git a/tools/lib/perf/include/perf/cpumap.h b/tools/lib/perf/include/perf/cpumap.h
> index 6a17ad730cbc..7c27766ea0bf 100644
> --- a/tools/lib/perf/include/perf/cpumap.h
> +++ b/tools/lib/perf/include/perf/cpumap.h
> @@ -9,6 +9,7 @@
> struct perf_cpu_map;
>
> LIBPERF_API struct perf_cpu_map *perf_cpu_map__dummy_new(void);
> +LIBPERF_API struct perf_cpu_map *perf_cpu_map__default_new(void);
> LIBPERF_API struct perf_cpu_map *perf_cpu_map__new(const char *cpu_list);
> LIBPERF_API struct perf_cpu_map *perf_cpu_map__read(FILE *file);
> LIBPERF_API struct perf_cpu_map *perf_cpu_map__get(struct perf_cpu_map *map);
>
prev parent reply other threads:[~2021-06-30 12:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 14:33 [PATCH v2 1/3] libperf: Add perf_cpu_map__default_new() Jin Yao
2021-06-21 14:33 ` [PATCH v2 2/3] perf tools: Create hybrid flag in target Jin Yao
2021-06-21 14:33 ` [PATCH v2 3/3] perf tools: Enable on a list of CPUs for hybrid Jin Yao
2021-06-30 12:35 ` Jin, Yao [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=858b4c6f-99dd-c0d8-d8ec-67f905b3287c@linux.intel.com \
--to=yao.jin@linux.intel.com \
--cc=Linux-kernel@vger.kernel.org \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=yao.jin@intel.com \
/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