From: Jiri Olsa <olsajiri@gmail.com>
To: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
Cc: acme@kernel.org, irogers@google.com, linux-perf-users@vger.kernel.org
Subject: Re: [PATCH] libperf: Rename arguments of perf_thread_map APIs
Date: Mon, 21 Feb 2022 20:46:40 +0100 [thread overview]
Message-ID: <YhPsIJBdsN9AiE0O@krava> (raw)
In-Reply-To: <20220221102612.43879-1-tz.stoyanov@gmail.com>
On Mon, Feb 21, 2022 at 12:26:12PM +0200, Tzvetomir Stoyanov (VMware) wrote:
> The "int thread" input arguments of some perf_thead_map APIs are index
> of the thread in the thread map. In order to avoid confusion and to
> make the APIs consistent with perf_cpu_map APIs, those arguments are
> renamed to "int idx".
>
> Suggested-by: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
> Signed-off-by: Tzvetomir Stoyanov (VMware) <tz.stoyanov@gmail.com>
> ---
> tools/lib/perf/Documentation/libperf.txt | 6 +++---
> tools/lib/perf/include/perf/threadmap.h | 6 +++---
> tools/lib/perf/threadmap.c | 12 ++++++------
> 3 files changed, 12 insertions(+), 12 deletions(-)
>
> diff --git a/tools/lib/perf/Documentation/libperf.txt b/tools/lib/perf/Documentation/libperf.txt
> index 32c5051c24eb..a21f733b95b1 100644
> --- a/tools/lib/perf/Documentation/libperf.txt
> +++ b/tools/lib/perf/Documentation/libperf.txt
> @@ -63,10 +63,10 @@ SYNOPSIS
>
> struct perf_thread_map *perf_thread_map__new_dummy(void);
>
> - void perf_thread_map__set_pid(struct perf_thread_map *map, int thread, pid_t pid);
> - char *perf_thread_map__comm(struct perf_thread_map *map, int thread);
> + void perf_thread_map__set_pid(struct perf_thread_map *map, int idx, pid_t pid);
> + char *perf_thread_map__comm(struct perf_thread_map *map, int idx);
> int perf_thread_map__nr(struct perf_thread_map *threads);
> - pid_t perf_thread_map__pid(struct perf_thread_map *map, int thread);
> + pid_t perf_thread_map__pid(struct perf_thread_map *map, int idx);
>
> struct perf_thread_map *perf_thread_map__get(struct perf_thread_map *map);
> void perf_thread_map__put(struct perf_thread_map *map);
> diff --git a/tools/lib/perf/include/perf/threadmap.h b/tools/lib/perf/include/perf/threadmap.h
> index a7c50de8d010..58f7fbdce446 100644
> --- a/tools/lib/perf/include/perf/threadmap.h
> +++ b/tools/lib/perf/include/perf/threadmap.h
> @@ -9,10 +9,10 @@ struct perf_thread_map;
>
> LIBPERF_API struct perf_thread_map *perf_thread_map__new_dummy(void);
>
> -LIBPERF_API void perf_thread_map__set_pid(struct perf_thread_map *map, int thread, pid_t pid);
> -LIBPERF_API char *perf_thread_map__comm(struct perf_thread_map *map, int thread);
> +LIBPERF_API void perf_thread_map__set_pid(struct perf_thread_map *map, int idx, pid_t pid);
> +LIBPERF_API char *perf_thread_map__comm(struct perf_thread_map *map, int idx);
> LIBPERF_API int perf_thread_map__nr(struct perf_thread_map *threads);
> -LIBPERF_API pid_t perf_thread_map__pid(struct perf_thread_map *map, int thread);
> +LIBPERF_API pid_t perf_thread_map__pid(struct perf_thread_map *map, int idx);
does this argument name change break abi? do we care at this point? ;-)
not sure if we already started to treat libperf properly in this regard
jirka
next prev parent reply other threads:[~2022-02-21 19:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 10:26 [PATCH] libperf: Rename arguments of perf_thread_map APIs Tzvetomir Stoyanov (VMware)
2022-02-21 19:46 ` Jiri Olsa [this message]
2022-02-21 20:02 ` Arnaldo Carvalho de Melo
2022-02-23 15:27 ` Arnaldo Carvalho de Melo
2022-02-23 17:14 ` Jiri Olsa
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=YhPsIJBdsN9AiE0O@krava \
--to=olsajiri@gmail.com \
--cc=acme@kernel.org \
--cc=irogers@google.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=tz.stoyanov@gmail.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