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 1/2] tools/perf: Fix the string match for "/tmp/perf-$PID.map" files in dso__load
Date: Sun, 16 Jun 2024 18:37:01 +0300 [thread overview]
Message-ID: <5d9a9842-9b8a-428c-898f-e1ff866a6e66@intel.com> (raw)
In-Reply-To: <20240614172742.56976-1-atrajeev@linux.vnet.ibm.com>
On 14/06/24 20:27, Athira Rajeev wrote:
> Perf test for perf probe of function from different CU fails
> as below:
>
> ./perf test -vv "test perf probe of function from different CU"
> 116: test perf probe of function from different CU:
> --- start ---
> test child forked, pid 2679
> Failed to find symbol foo in /tmp/perf-uprobe-different-cu-sh.Msa7iy89bx/testfile
> Error: Failed to add events.
> --- Cleaning up ---
> "foo" does not hit any event.
> Error: Failed to delete events.
> ---- end(-1) ----
> 116: test perf probe of function from different CU : FAILED!
>
> The test does below to probe function "foo" :
>
> # gcc -g -Og -flto -c /tmp/perf-uprobe-different-cu-sh.XniNxNEVT7/testfile-foo.c
> -o /tmp/perf-uprobe-different-cu-sh.XniNxNEVT7/testfile-foo.o
> # gcc -g -Og -c /tmp/perf-uprobe-different-cu-sh.XniNxNEVT7/testfile-main.c
> -o /tmp/perf-uprobe-different-cu-sh.XniNxNEVT7/testfile-main.o
> # gcc -g -Og -o /tmp/perf-uprobe-different-cu-sh.XniNxNEVT7/testfile
> /tmp/perf-uprobe-different-cu-sh.XniNxNEVT7/testfile-foo.o
> /tmp/perf-uprobe-different-cu-sh.XniNxNEVT7/testfile-main.o
>
> # ./perf probe -x /tmp/perf-uprobe-different-cu-sh.XniNxNEVT7/testfile foo
> Failed to find symbol foo in /tmp/perf-uprobe-different-cu-sh.XniNxNEVT7/testfile
> Error: Failed to add events.
>
> Perf probe fails to find symbol foo in the executable placed in
> /tmp/perf-uprobe-different-cu-sh.XniNxNEVT7
>
> Simple reproduce:
>
> # mktemp -d /tmp/perf-checkXXXXXXXXXX
> /tmp/perf-checkcWpuLRQI8j
>
> # gcc -g -o test test.c
> # cp test /tmp/perf-checkcWpuLRQI8j/
> # nm /tmp/perf-checkcWpuLRQI8j/test | grep foo
> 00000000100006bc T foo
>
> # ./perf probe -x /tmp/perf-checkcWpuLRQI8j/test foo
> Failed to find symbol foo in /tmp/perf-checkcWpuLRQI8j/test
> Error: Failed to add events.
>
> But it works with any files like /tmp/perf/test. Only for
> patterns with "/tmp/perf-", this fails.
>
> Further debugging, 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" .
>
> The check used "if (strncmp(self->name, "/tmp/perf-", 10) == 0)"
> to match "/tmp/perf-$PID.map". With this commit, any dso in
> /tmp/perf- folder will be considered separately for processing
> (not only JIT created map files ). Fix this by changing the
> string pattern to check for regex of form "/tmp/perf-*.map"
>
> With the fix,
> # ./perf test "test perf probe of function from different CU"
> 117: test perf probe of function from different CU : Ok
>
> Signed-off-by: Athira Rajeev<atrajeev@linux.vnet.ibm.com>
> ---
> tools/perf/util/symbol.c | 12 +++++++++++-
> 1 file changed, 11 insertions(+), 1 deletion(-)
>
> diff --git a/tools/perf/util/symbol.c b/tools/perf/util/symbol.c
> index 9e5940b5bc59..bfb88a4b0987 100644
> --- a/tools/perf/util/symbol.c
> +++ b/tools/perf/util/symbol.c
> @@ -41,6 +41,7 @@
> #include <limits.h>
> #include <symbol/kallsyms.h>
> #include <sys/utsname.h>
> +#include <regex.h>
>
> static int dso__load_kernel_sym(struct dso *dso, struct map *map);
> static int dso__load_guest_kernel_sym(struct dso *dso, struct map *map);
> @@ -1797,9 +1798,18 @@ int dso__load(struct dso *dso, struct map *map)
> struct nscookie nsc;
> char newmapname[PATH_MAX];
> const char *map_path = dso__long_name(dso);
> + regex_t regex;
> + const char *pattern = "(^/tmp/perf-).*(map)";
>
> mutex_lock(dso__lock(dso));
> - perfmap = strncmp(dso__name(dso), "/tmp/perf-", 10) == 0;
> + if (regcomp(®ex, pattern, REG_EXTENDED)) {
> + pr_debug("regcomp() failed in dso__load\n");
> + ret = -1;
> + goto out;
> + }
> +
> + perfmap = !regexec(®ex, dso__name(dso), 0, NULL, 0);
This isn't the only place that checks for that name. Perhaps
create a helper function:
bool is_perf_pid_map_name(const char *name);
Regex looks over complicated. Maybe sscanf
int tid;
return sscanf(name, "/tmp/perf-%d.map", &tid) == 1;
> +
> if (perfmap) {
> if (dso__nsinfo(dso) &&
> (dso__find_perf_map(newmapname, sizeof(newmapname),
prev parent reply other threads:[~2024-06-16 15:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 17:27 [PATCH 1/2] tools/perf: Fix the string match for "/tmp/perf-$PID.map" files in dso__load Athira Rajeev
2024-06-14 17:27 ` [PATCH 2/2] tools/perf: Fix parallel-perf python script to replace new python syntax ":=" usage Athira Rajeev
2024-06-16 15:03 ` Adrian Hunter
2024-06-17 9:02 ` Athira Rajeev
2024-06-16 15:37 ` Adrian Hunter [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=5d9a9842-9b8a-428c-898f-e1ff866a6e66@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).