From: Adrian Hunter <adrian.hunter@intel.com>
To: Athira Rajeev <atrajeev@linux.vnet.ibm.com>,
acme@kernel.org, jolsa@kernel.org, irogers@google.com,
namhyung@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, akanksha@linux.ibm.com,
maddy@linux.ibm.com, kjain@linux.ibm.com,
disgoel@linux.vnet.ibm.com
Subject: Re: [PATCH V4 2/3] tools/perf: Use is_perf_pid_map_name helper function to check dso's of pattern /tmp/perf-%d.map
Date: Tue, 25 Jun 2024 15:03:03 +0300 [thread overview]
Message-ID: <536ccca7-278c-4d50-9c24-bf4409cd75dc@intel.com> (raw)
In-Reply-To: <20240623064850.83720-2-atrajeev@linux.vnet.ibm.com>
On 23/06/24 09:48, Athira Rajeev wrote:
> commit 80d496be89ed ("perf report: Add support for profiling JIT
> generated code") added support for profiling JIT generated code.
> This patch handles dso's of form "/tmp/perf-$PID.map".
>
> Some of the references doesn't check exactly for same pattern.
> some uses "if (!strncmp(dso_name, "/tmp/perf-", 10))". Fix
> this by using helper function perf_pid_map_tid and
> is_perf_pid_map_name which looks for proper pattern of
> form: "/tmp/perf-$PID.map" for these checks.
>
> Signed-off-by: Athira Rajeev <atrajeev@linux.vnet.ibm.com>
Add a Fixes tag, then
Reviewed-by: Adrian Hunter <adrian.hunter@intel.com>
> ---
> tools/perf/util/dsos.c | 2 +-
> tools/perf/util/srcline.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/tools/perf/util/dsos.c b/tools/perf/util/dsos.c
> index ab3d0c01dd63..846828ea1f00 100644
> --- a/tools/perf/util/dsos.c
> +++ b/tools/perf/util/dsos.c
> @@ -275,7 +275,7 @@ static void dso__set_basename(struct dso *dso)
> char *base, *lname;
> int tid;
>
> - if (sscanf(dso__long_name(dso), "/tmp/perf-%d.map", &tid) == 1) {
> + if (perf_pid_map_tid(dso__long_name(dso), &tid)) {
> if (asprintf(&base, "[JIT] tid %d", tid) < 0)
> return;
> } else {
> diff --git a/tools/perf/util/srcline.c b/tools/perf/util/srcline.c
> index 9d670d8c1c08..51eb78993fe2 100644
> --- a/tools/perf/util/srcline.c
> +++ b/tools/perf/util/srcline.c
> @@ -39,7 +39,7 @@ static const char *srcline_dso_name(struct dso *dso)
> if (dso_name[0] == '[')
> return NULL;
>
> - if (!strncmp(dso_name, "/tmp/perf-", 10))
> + if (is_perf_pid_map_name(dso_name))
> return NULL;
>
> return dso_name;
WARNING: multiple messages have this Message-ID (diff)
From: Adrian Hunter <adrian.hunter@intel.com>
To: Athira Rajeev <atrajeev@linux.vnet.ibm.com>,
acme@kernel.org, jolsa@kernel.org, irogers@google.com,
namhyung@kernel.org
Cc: maddy@linux.ibm.com, kjain@linux.ibm.com,
linux-kernel@vger.kernel.org, akanksha@linux.ibm.com,
linux-perf-users@vger.kernel.org, disgoel@linux.vnet.ibm.com,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH V4 2/3] tools/perf: Use is_perf_pid_map_name helper function to check dso's of pattern /tmp/perf-%d.map
Date: Tue, 25 Jun 2024 15:03:03 +0300 [thread overview]
Message-ID: <536ccca7-278c-4d50-9c24-bf4409cd75dc@intel.com> (raw)
In-Reply-To: <20240623064850.83720-2-atrajeev@linux.vnet.ibm.com>
On 23/06/24 09:48, Athira Rajeev wrote:
> commit 80d496be89ed ("perf report: Add support for profiling JIT
> generated code") added support for profiling JIT generated code.
> This patch handles dso's of form "/tmp/perf-$PID.map".
>
> Some of the references doesn't check exactly for same pattern.
> some uses "if (!strncmp(dso_name, "/tmp/perf-", 10))". Fix
> this by using helper function perf_pid_map_tid and
> is_perf_pid_map_name which looks for proper pattern of
> form: "/tmp/perf-$PID.map" for these checks.
>
> Signed-off-by: Athira Rajeev <atrajeev@linux.vnet.ibm.com>
Add a Fixes tag, then
Reviewed-by: Adrian Hunter <adrian.hunter@intel.com>
> ---
> tools/perf/util/dsos.c | 2 +-
> tools/perf/util/srcline.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/tools/perf/util/dsos.c b/tools/perf/util/dsos.c
> index ab3d0c01dd63..846828ea1f00 100644
> --- a/tools/perf/util/dsos.c
> +++ b/tools/perf/util/dsos.c
> @@ -275,7 +275,7 @@ static void dso__set_basename(struct dso *dso)
> char *base, *lname;
> int tid;
>
> - if (sscanf(dso__long_name(dso), "/tmp/perf-%d.map", &tid) == 1) {
> + if (perf_pid_map_tid(dso__long_name(dso), &tid)) {
> if (asprintf(&base, "[JIT] tid %d", tid) < 0)
> return;
> } else {
> diff --git a/tools/perf/util/srcline.c b/tools/perf/util/srcline.c
> index 9d670d8c1c08..51eb78993fe2 100644
> --- a/tools/perf/util/srcline.c
> +++ b/tools/perf/util/srcline.c
> @@ -39,7 +39,7 @@ static const char *srcline_dso_name(struct dso *dso)
> if (dso_name[0] == '[')
> return NULL;
>
> - if (!strncmp(dso_name, "/tmp/perf-", 10))
> + if (is_perf_pid_map_name(dso_name))
> return NULL;
>
> return dso_name;
next prev parent reply other threads:[~2024-06-25 12:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-23 6:48 [PATCH V4 1/3] tools/perf: Fix the string match for "/tmp/perf-$PID.map" files in dso__load Athira Rajeev
2024-06-23 6:48 ` Athira Rajeev
2024-06-23 6:48 ` [PATCH V4 2/3] tools/perf: Use is_perf_pid_map_name helper function to check dso's of pattern /tmp/perf-%d.map Athira Rajeev
2024-06-23 6:48 ` Athira Rajeev
2024-06-25 12:03 ` Adrian Hunter [this message]
2024-06-25 12:03 ` Adrian Hunter
2024-06-25 18:06 ` Namhyung Kim
2024-06-25 18:06 ` Namhyung Kim
2024-06-23 6:48 ` [PATCH V4 3/3] tools/perf: Fix parallel-perf python script to replace new python syntax ":=" usage Athira Rajeev
2024-06-23 6:48 ` Athira Rajeev
2024-06-25 11:57 ` [PATCH V4 1/3] tools/perf: Fix the string match for "/tmp/perf-$PID.map" files in dso__load Adrian Hunter
2024-06-25 11:57 ` Adrian Hunter
2024-06-25 12:02 ` Adrian Hunter
2024-06-25 12:02 ` Adrian Hunter
2024-06-25 17:59 ` Namhyung Kim
2024-06-25 17:59 ` Namhyung Kim
2024-06-26 5:04 ` Athira Rajeev
2024-06-26 5:04 ` Athira Rajeev
2024-06-26 3:55 ` Namhyung Kim
2024-06-26 3:55 ` Namhyung Kim
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=536ccca7-278c-4d50-9c24-bf4409cd75dc@intel.com \
--to=adrian.hunter@intel.com \
--cc=acme@kernel.org \
--cc=akanksha@linux.ibm.com \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=disgoel@linux.vnet.ibm.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kjain@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--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.