From: Milian Wolff <milian.wolff@kdab.com>
To: linux-perf-users@vger.kernel.org
Cc: acme@kernel.org
Subject: perf trace & vfs_getname
Date: Tue, 24 May 2016 22:42:12 +0200 [thread overview]
Message-ID: <3503612.0WeV8glAT3@agathebauer> (raw)
[-- Attachment #1: Type: text/plain, Size: 2033 bytes --]
Hey Arnaldo,
I just wanted to try out your ongoing work to get file names printed in perf
trace:
~~~~~~~~~~~~~~
$ perf trace -e open ls builtin-trace.c
0.007 ( 0.007 ms): ls/26364 open(filename: 0x2a1b0d20, flags: CLOEXEC
) = -1 ENOENT No such file or directorybuiltin-trace.c
0.022 ( 0.002 ms): ls/26364 open(filename: 0x2a1b0d20, flags: CLOEXEC
) = -1 ENOENT No such file or directory
...
~~~~~~~~~~~~~~
So apparently I still have to manually create the probe for vfs_getname. Could
this be simplified for the user? E.g. by adding a static tracepoint for that
purpose, so one doesn't have to run `perf probe` manually? Also, note that
`vfs_getname` is only mentioned in `man perf trace` for its `--tool_stats`
parameter, but the actual line to create the probe is nowhere to be found.
Grepping the git log I found the following invocation, which errors out on my
Arch machine:
~~~~~~~~~~~~~~~
$ perf probe 'vfs_getname=getname_flags:72 pathname=filename:string'
The /home/milian/.debug/.build-id/1a/03b857e3611b7a14fbf60d67cad7415706a933
file has no debug information.
Rebuild with CONFIG_DEBUG_INFO=y, or install an appropriate debuginfo package.
Error: Failed to add events.
~~~~~~~~~~~~~~~
On a different Arch machine it's:
~~~~~~~~~~~~~~~
$ perf probe 'vfs_getname=getname_flags:72 pathname=filename:string'
The /lib/modules/4.5.4-1-ARCH/build/vmlinux file has no debug information.
Rebuild with CONFIG_DEBUG_INFO=y, or install an appropriate debuginfo package.
Error: Failed to add events.
~~~~~~~~~~~~~~~
On an Ubuntu 16.04 I'm getting this:
~~~~~~~~~~~~~~~
$ perf probe 'vfs_getname=getname_flags:72 pathname=filename:string'
Failed to find the path for kernel: No such file or directory
Error: Failed to add events.
~~~~~~~~~~~~~~~
So does this really mean I'm out of luck?
--
Milian Wolff | milian.wolff@kdab.com | Software Engineer
KDAB (Deutschland) GmbH&Co KG, a KDAB Group company
Tel: +49-30-521325470
KDAB - The Qt Experts
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5903 bytes --]
next reply other threads:[~2016-05-24 20:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 20:42 Milian Wolff [this message]
2016-05-24 22:21 ` perf trace & vfs_getname Arnaldo Carvalho de Melo
2016-05-25 18:00 ` Frank Ch. Eigler
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=3503612.0WeV8glAT3@agathebauer \
--to=milian.wolff@kdab.com \
--cc=acme@kernel.org \
--cc=linux-perf-users@vger.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