From: James Clark <james.clark@arm.com>
To: Athira Rajeev <atrajeev@linux.vnet.ibm.com>
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, acme@kernel.org, jolsa@kernel.org,
adrian.hunter@intel.com, irogers@google.com, namhyung@kernel.org
Subject: Re: [PATCH V2 2/3] tools/perf: Use is_perf_pid_map_name helper function to check dso's of pattern /tmp/perf-%d.map
Date: Mon, 17 Jun 2024 14:59:22 +0100 [thread overview]
Message-ID: <30cdabb5-4c36-40c6-a2c0-8059e4afb371@arm.com> (raw)
In-Reply-To: <20240617130332.13427-2-atrajeev@linux.vnet.ibm.com>
On 17/06/2024 14:03, 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 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>
> ---
> 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..23cd02aa701d 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 (is_perf_pid_map_name(dso__long_name(dso))) {
> 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;
Duplicate of [1] but the latest version of the other one looks like it
might have a mistake in it.
For this one I get this compilation error:
util/dsos.c: In function ‘dso__set_basename’:
util/dsos.c:279:21: error: ‘tid’ may be used uninitialized
[-Werror=maybe-uninitialized]
279 | if (asprintf(&base, "[JIT] tid %d", tid) < 0)
[1]:
https://lore.kernel.org/linux-perf-users/20240601125946.1741414-10-ChaitanyaS.Prakash@arm.com/
next prev parent reply other threads:[~2024-06-17 13:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 13:03 [PATCH V2 1/3] tools/perf: Fix the string match for "/tmp/perf-$PID.map" files in dso__load Athira Rajeev
2024-06-17 13:03 ` [PATCH V2 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-17 13:59 ` James Clark [this message]
2024-06-17 16:53 ` Athira Rajeev
2024-06-18 7:11 ` Adrian Hunter
2024-06-18 9:26 ` Athira Rajeev
2024-06-17 13:03 ` [PATCH V2 3/3] tools/perf: Fix parallel-perf python script to replace new python syntax ":=" usage Athira Rajeev
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=30cdabb5-4c36-40c6-a2c0-8059e4afb371@arm.com \
--to=james.clark@arm.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®