From: Athira Rajeev <atrajeev@linux.vnet.ibm.com>
To: Namhyung Kim <namhyung@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-perf-users <linux-perf-users@vger.kernel.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
akanksha@linux.ibm.com, Madhavan Srinivasan <maddy@linux.ibm.com>,
Kajol Jain <kjain@linux.ibm.com>,
Disha Goel <disgoel@linux.vnet.ibm.com>
Subject: Re: [PATCH V4 1/3] tools/perf: Fix the string match for "/tmp/perf-$PID.map" files in dso__load
Date: Wed, 26 Jun 2024 10:34:06 +0530 [thread overview]
Message-ID: <41C6FBA0-98FB-458A-AA01-77B9604D56C2@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAM9d7ci2raJmUjb7X2m6O1mCJm5xYLEWS8g_gC7tTjvshm1XFQ@mail.gmail.com>
> On 25 Jun 2024, at 11:29 PM, Namhyung Kim <namhyung@kernel.org> wrote:
>
> Hello,
>
> On Tue, Jun 25, 2024 at 5:02 AM Adrian Hunter <adrian.hunter@intel.com> wrote:
>>
>> On 25/06/24 14:57, Adrian Hunter wrote:
>>> On 23/06/24 09:48, 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 "/tmp/perf-%d.map". Add a helper
>>>> function is_perf_pid_map_name to do this check. In "struct dso",
>>>> dso->long_name holds the long name of the dso file. Since the
>>>> /tmp/perf-$PID.map check uses the complete name, use dso___long_name for
>>>> the string name.
>>>>
>>>> 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>
>>>
>>> Reviewed-by: Adrian Hunter <adrian.hunter@intel.com>
>>>
>>
>> Although it could use a Fixes tag
>>
>
> Thanks, I will add
>
> Fixes: 56cbeacf1435 ("perf probe: Add test for regression introduced
> by switch to die_get_decl_file()")
>
> Namhyung
>
Hi Adrian,
Thanks for the review.
Thanks Namhyung for adding the Fixes tag and pulling the fix
Athira
next prev parent reply other threads:[~2024-06-26 5:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
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-25 12:03 ` Adrian Hunter
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-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 12:02 ` Adrian Hunter
2024-06-25 17:59 ` Namhyung Kim
2024-06-26 5:04 ` Athira Rajeev [this message]
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=41C6FBA0-98FB-458A-AA01-77B9604D56C2@linux.vnet.ibm.com \
--to=atrajeev@linux.vnet.ibm.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=akanksha@linux.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®