From: "Wangnan (F)" <wangnan0@huawei.com>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: perf test BPF failing on f24: fix
Date: Thu, 4 Aug 2016 09:50:25 +0800 [thread overview]
Message-ID: <57A29F61.5050702@huawei.com> (raw)
In-Reply-To: <20160804080800.a056b02044c1e749bac02cbe@kernel.org>
On 2016/8/4 7:08, Masami Hiramatsu wrote:
> On Wed, 3 Aug 2016 23:45:57 +0900
> Masami Hiramatsu <mhiramat@kernel.org> wrote:
>
>>>> [root@jouet ~]# perf probe sys_epoll_wait
>>>> Failed to find debug information for address ffffffffbd295b50
>>>> Probe point 'sys_epoll_wait' not found.
>>>> Error: Failed to add events.
>> So, at least I should investigate it.
> FYI, on ubuntu16.04, I can put probes on sys_epoll_wait as below
>
> mhiramat@devnote:~/ksrc/linux/tools/perf$ sudo ./perf probe -vnf sys_epoll_wait
> probe-definition(0): sys_epoll_wait
> symbol:sys_epoll_wait file:(null) line:0 offset:0 return:0 lazy:(null)
> 0 arguments
> Looking at the vmlinux_path (8 entries long)
> Using /usr/lib/debug/boot/vmlinux-4.4.0-31-generic for symbols
> Open Debuginfo file: /usr/lib/debug/boot/vmlinux-4.4.0-31-generic
> Try to find probe point from debuginfo.
> Symbol sys_epoll_wait address found : ffffffff81257410
> Matched function: SyS_epoll_wait
> found inline addr: 0xffffffff81257410
> Probe point found: SyS_epoll_wait+0
> found inline addr: 0xffffffff8125756d
> Probe point found: SyS_epoll_pwait+141
> found inline addr: 0xffffffff81257793
> Probe point found: compat_SyS_epoll_pwait+147
> Found 3 probe_trace_events.
> Opening /sys/kernel/debug/tracing//kprobe_events write=1
> Writing event: p:probe/sys_epoll_wait _text+2454544
> Writing event: p:probe/sys_epoll_wait_1 _text+2454893
> Writing event: p:probe/sys_epoll_wait_2 _text+2455443
> Added new events:
> probe:sys_epoll_wait (on sys_epoll_wait)
> probe:sys_epoll_wait_1 (on sys_epoll_wait)
> probe:sys_epoll_wait_2 (on sys_epoll_wait)
>
> You can now use it in all perf tools, such as:
>
> perf record -e probe:sys_epoll_wait_2 -aR sleep 1
>
Have you checked 'readelf -wi'? I guess you wouldn't find
sys_epoll_wait.
Thank you.
next prev parent reply other threads:[~2016-08-04 1:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 19:51 perf test BPF failing on f24: fix Arnaldo Carvalho de Melo
2016-08-02 21:03 ` Alexei Starovoitov
2016-08-03 2:15 ` Arnaldo Carvalho de Melo
2016-08-03 2:57 ` Alexei Starovoitov
2016-08-03 2:41 ` Wangnan (F)
2016-08-03 3:41 ` Wangnan (F)
2016-08-03 8:19 ` Wangnan (F)
2016-08-03 14:45 ` Masami Hiramatsu
2016-08-03 20:04 ` Arnaldo Carvalho de Melo
2016-08-04 6:32 ` Masami Hiramatsu
2016-08-04 12:48 ` Arnaldo Carvalho de Melo
2016-08-04 19:36 ` Arnaldo Carvalho de Melo
2016-08-04 21:47 ` Arnaldo Carvalho de Melo
2016-08-05 9:45 ` Masami Hiramatsu
2016-08-05 14:35 ` Arnaldo Carvalho de Melo
2016-08-05 15:55 ` Arnaldo Carvalho de Melo
2016-08-06 10:29 ` Masami Hiramatsu
2016-08-08 19:33 ` Arnaldo Carvalho de Melo
2016-08-09 19:17 ` [tip:perf/urgent] perf probe: Adjust map->reloc offset when finding kernel symbol from map tip-bot for Masami Hiramatsu
2016-08-03 23:08 ` perf test BPF failing on f24: fix Masami Hiramatsu
2016-08-04 1:50 ` Wangnan (F) [this message]
2016-08-04 8:47 ` Masami Hiramatsu
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=57A29F61.5050702@huawei.com \
--to=wangnan0@huawei.com \
--cc=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.