From: Li Zhijian <zhijianx.li@intel.com>
To: acme@kernel.org
Cc: linux-kernel@vger.kernel.org, "Li, Philip" <philip.li@intel.com>
Subject: perf test vfs_getname failed
Date: Thu, 19 Oct 2017 16:31:36 +0800 [thread overview]
Message-ID: <48d01197-5676-40f6-ba16-72d3010b095f@intel.com> (raw)
Hi Arnaldo
i encounter some problem when running perf test, the details arelike below:
-----------------------------
[lizj@rhel71 perf]$ sudo ./perf test vfs_getname -v
61: Add vfs_getname probe to get syscall args filenames :
--- start ---
test child forked, pid 5958
Failed to find 'result' in this function.
Error: Failed to add events.
test child finished with -1
---- end ----
Add vfs_getname probe to get syscall args filenames: FAILED!
62: Use vfs_getname probe to get syscall args filenames :
--- start ---
test child forked, pid 5979
Failed to find 'result' in this function.
Error: Failed to add events.
test child finished with -1
---- end ----
Use vfs_getname probe to get syscall args filenames: FAILED!
63: Check open filename arg using perf trace + vfs_getname:
--- start ---
test child forked, pid 6001
Failed to find 'result' in this function.
Error: Failed to add events.
test child finished with -1
---- end ----
Check open filename arg using perf trace + vfs_getname: FAILED!
-----------------------------
my environment:
1. perf features
the enabled features are:
-----------------------------
Auto-detecting system features:
... dwarf: [ on ]
... dwarf_getlocations: [ on ]
... glibc: [ on ]
... gtk2: [ on ]
... libaudit: [ on ]
... libbfd: [ on ]
... libelf: [ on ]
... libnuma: [ on ]
... numa_num_possible_cpus: [ on ]
... libperl: [ on ]
... libpython: [ on ]
... libslang: [ OFF ]
... libcrypto: [ on ]
... libunwind: [ on ]
... libdw-dwarf-unwind: [ on ]
... zlib: [ on ]
... lzma: [ on ]
... get_cpuid: [ on ]
... bpf: [ on ]
-----------------------------
2. host
[lizj@rhel71 perf]$ cat /etc/redhat-release
Red Hat Enterprise Linux Server release 7.1 Beta (Maipo)
3. kernel
[lizj@rhel71 perf]$ uname -a
Linux rhel71 4.14.0-rc1+ #2 SMP Wed Oct 18 23:49:30 EDT 2017 x86_64 x86_64 x86_64 GNU/Linux
if i miss something, fell free to let me know :)
Thanks
Zhijian
next reply other threads:[~2017-10-19 8:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 8:31 Li Zhijian [this message]
2017-10-23 9:38 ` Li Zhijian
2017-10-23 14:24 ` Arnaldo Carvalho de Melo
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=48d01197-5676-40f6-ba16-72d3010b095f@intel.com \
--to=zhijianx.li@intel.com \
--cc=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=philip.li@intel.com \
/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®