From: He Kuang <hekuang@huawei.com>
To: <ast@plumgrid.com>, <davem@davemloft.net>, <acme@kernel.org>,
<mingo@redhat.com>, <a.p.zijlstra@chello.nl>,
<masami.hiramatsu.pt@hitachi.com>, <jolsa@kernel.org>
Cc: <wangnan0@huawei.com>, <lizefan@kernel.org>,
<linux-kernel@vger.kernel.org>, <pi3orama@163.com>
Subject: [RFC PATCH 0/6] perf bpf: Probing with local variable
Date: Tue, 5 May 2015 10:10:06 +0000 [thread overview]
Message-ID: <1430820612-84443-1-git-send-email-hekuang@huawei.com> (raw)
This patch set is based on https://lkml.org/lkml/2015/4/30/264
By using bpf 'config' section like this:
char _config2[] SEC("config") = "generic_perform_write=generic_perform_write+122 file->f_mapping->a_ops bytes offset";
SEC("generic_perform_write")
int NODE_generic_perform_write (struct pt_regs *ctx, void *a_ops, void *bytes, void* offset) {
char fmt[] = "NODE_generic_perform_write, a_ops=%p, bytes=%p, offset=%p\n";
bpf_trace_printk(fmt, sizeof(fmt), a_ops, bytes, offset);
return 1;
}
In this example, 'bytes' and 'offset' are local variables, a_ops is in
the structure field of file parameter, and we probe in the body of the
generic_perform_write() function.
Perf can fetch and convert all the arguments and then we translate them
into bpf bytecode as a prologue before calling bpf body functions. In
the prologue, we fetch arguments from bpf context register and place
them according to bpf calling conventions so the body function can
access them as formal parameters.
The perf command is as following:
$ perf bpf -v bpf_bytecode.o
...
bpf_prologue: insn num=26
(bf) r6 = r1
(79) r3 = *(u64 *)(r6 +112)
(07) r3 += 248
(b7) r1 = 0
(7b) *(u64 *)(r10 -8) = r1
(bf) r1 = r10
(07) r1 += -8
(b7) r2 = 8
(85) call 4
(79) r3 = *(u64 *)(r10 -8)
(07) r3 += 104
(b7) r1 = 0
(7b) *(u64 *)(r10 -8) = r1
(bf) r1 = r10
(07) r1 += -8
(b7) r2 = 8
(85) call 4
(79) r3 = *(u64 *)(r10 -8)
(bf) r7 = r3
(79) r3 = *(u64 *)(r6 +24)
(bf) r8 = r3
(79) r3 = *(u64 *)(r6 +88)
(bf) r9 = r3
(bf) r2 = r7
(bf) r3 = r8
(bf) r4 = r9
...
Added new event:
Writing event: p:perf_bpf_probe/generic_perform_write _stext+1257282 a_ops=+104(+248(%di)):u64 bytes=%r12:u64 offset=%cx:u64
perf_bpf_probe:generic_perform_write (on generic_perform_write+122 with a_ops=file->f_mapping->a_ops bytes offset)
The trace output:
sh-1260 [000] d... 112592.463169: : NODE_generic_perform_write, a_ops=ffffffff81a20160, bytes=0000000000000017, offset=000000000000031d
sh-1260 [000] d... 112593.155105: : NODE_generic_perform_write, a_ops=ffffffff81a20160, bytes=000000000000000a, offset=0000000000000334
sh-1260 [000] d... 112599.015993: : NODE_generic_perform_write, a_ops=ffffffff81a20160, bytes=0000000000000017, offset=000000000000033e
sh-1260 [000] d... 112600.790977: : NODE_generic_perform_write, a_ops=ffffffff81a20160, bytes=000000000000000a, offset=0000000000000355
He Kuang (6):
perf bpf: Add headers for generate bpf bytecode
perf bpf: Add pt_regs convert table for x86
perf bpf: Save pt_regs info from debuginfo
perf bpf: Convert arglist to bpf prologue
perf bpf: Process debuginfo for generating bpf prologue
perf bpf: Generate bpf prologue for arguments
tools/perf/arch/x86/util/dwarf-regs.c | 31 ++++++
tools/perf/util/bpf-loader.c | 66 ++++++++++++
tools/perf/util/bpf-loader.h | 188 ++++++++++++++++++++++++++++++++++
tools/perf/util/include/dwarf-regs.h | 2 +
tools/perf/util/probe-event.c | 121 ++++++++++++++++++++++
tools/perf/util/probe-event.h | 12 +++
tools/perf/util/probe-finder.c | 101 ++++++++++++++++++
tools/perf/util/probe-finder.h | 4 +
8 files changed, 525 insertions(+)
--
1.8.5.2
next reply other threads:[~2015-05-05 10:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 10:10 He Kuang [this message]
2015-05-05 10:10 ` [RFC PATCH 1/6] perf bpf: Add headers for generate bpf bytecode He Kuang
2015-05-05 22:38 ` Alexei Starovoitov
2015-05-05 10:10 ` [RFC PATCH 2/6] perf bpf: Add pt_regs convert table for x86 He Kuang
2015-05-05 22:44 ` Alexei Starovoitov
2015-05-08 8:02 ` Masami Hiramatsu
2015-05-05 10:10 ` [RFC PATCH 3/6] perf bpf: Save pt_regs info from debuginfo He Kuang
2015-05-05 10:10 ` [RFC PATCH 4/6] perf bpf: Convert arglist to bpf prologue He Kuang
2015-05-05 22:54 ` Alexei Starovoitov
2015-05-05 10:10 ` [RFC PATCH 5/6] perf bpf: Process debuginfo for generating " He Kuang
2015-05-05 10:10 ` [RFC PATCH 6/6] perf bpf: Generate bpf prologue for arguments He Kuang
2015-05-05 22:31 ` [RFC PATCH 0/6] perf bpf: Probing with local variable Alexei Starovoitov
2015-05-06 3:58 ` Wang Nan
2015-05-06 4:10 ` Alexei Starovoitov
2015-05-06 4:41 ` Wang Nan
2015-05-06 1:37 ` Masami Hiramatsu
2015-05-06 1:44 ` 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=1430820612-84443-1-git-send-email-hekuang@huawei.com \
--to=hekuang@huawei.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=ast@plumgrid.com \
--cc=davem@davemloft.net \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@redhat.com \
--cc=pi3orama@163.com \
--cc=wangnan0@huawei.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®