From: Alexei Starovoitov <ast@plumgrid.com>
To: Wang Nan <wangnan0@huawei.com>,
acme@kernel.org, brendan.d.gregg@gmail.com, daniel@iogearbox.net,
namhyung@kernel.org, masami.hiramatsu.pt@hitachi.com,
paulus@samba.org, a.p.zijlstra@chello.nl, mingo@redhat.com,
jolsa@kernel.org, dsahern@gmail.com
Cc: linux-kernel@vger.kernel.org, lizefan@huawei.com,
hekuang@huawei.com, xiakaixu@huawei.com, pi3orama@163.com
Subject: Re: [RFC PATCH v7 00/37] perf tools: filtering events using eBPF programs
Date: Fri, 12 Jun 2015 09:58:28 -0700 [thread overview]
Message-ID: <557B0FB4.6000506@plumgrid.com> (raw)
In-Reply-To: <1434087345-127225-1-git-send-email-wangnan0@huawei.com>
On 6/11/15 10:35 PM, Wang Nan wrote:
> This is the 7th version which tries to introduce eBPF programs to perf.
> It enables 'perf record' to filter events using eBPF programs like:
>
> # perf record --event bpf-file.c sleep 1
>
> and
>
> # perf record --event bpf-file.o sleep 1
>
> This patch series is based on tip/perf/core (028c63b).
>
> Compare with v6 patch, this series totally refactor code for llvm
> compiling '.c' into BPF object file using LLVM. Including:
>
> 1. A specific file tools/perf/util/llvm-utils.c is introduced for
> holding all llvm/clang related work, instead of putting them into
> bpf-loader.c.
>
> 2. Automatically detect kernel include options by embedded shell
> script.
>
> 3. Use command line template to generate compiler commands instead of
> assemble cmdline with printf, passing variables using environment.
> Which enable users to define their own compiler commands.
>
> 4. Introduce '[llvm]' section to perf default config.
> 5 options can be configured, but all of them can be omitted:
>
> [llvm]
> # Path to clang. If omit, search it from $PATH.
> clang-path = "/path/to/clang"
>
> # Cmdline template. Following line shows its default value.
> # Environment variable is used to passing options.
> clang-bpf-cmd-template = "$CLANG_EXEC $CLANG_OPTIONS $KERNEL_INC_OPTIONS -Wno-unused-value -Wno-pointer-sign -working-directory $WORKING_DIR -c $CLANG_SOURCE -target bpf -O2 -o -"
>
> # Option passed to clang, will be passed to cmdline by $CLANG_OPTIONS.
> clang-opt = "-Wno-unused-value -Wno-pointer-sign"
>
> # kbuild directory. If not set, use /lib/modules/`uname -r`/build.
> # If set to "" deliberately, skip kernel header auto-detector.
> kbuild-dir = "/path/to/kernel/build"
>
> # Options passed to 'make' when detecting kernel header options.
> kbuild-opts = "ARCH=x86_64"
>
> Command line options '--clang-path' and '--clang-opt' is appended to
> 'perf record'.
>
> 5. LLVM and BPF opening testcase is adding into 'perf test':
>
> # perf test 37
> 37: Test LLVM searching and compiling : Ok
>
> 6. Warning and error messages improvement.
>
> 7. Issue clang command suit for newest clang which support
> '-target bpf', instead of calling
> 'clang -emit-llvm | llc -march=bpf' pipe.
All looks great to me.
Piping clang into stdout to skip .o on a disk is a nice touch.
'usability hints' have improved as well.
Thanks a lot for the hard work.
btw, what compile times do you see?
On my machine compiling basic hello_world.c with #include bpf_helpers.h
and few kernel headers take: 0.02 sec
So using .c is quite instant. Feels like interpreted language ;)
next prev parent reply other threads:[~2015-06-12 16:58 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-12 5:35 [RFC PATCH v7 00/37] perf tools: filtering events using eBPF programs Wang Nan
2015-06-12 5:35 ` [RFC PATCH v7 01/37] tools build: Add feature check for eBPF API Wang Nan
2015-06-12 5:35 ` [RFC PATCH v7 02/37] bpf tools: Introduce 'bpf' library to tools Wang Nan
2015-06-12 5:35 ` [RFC PATCH v7 03/37] bpf tools: Allow caller to set printing function Wang Nan
2015-06-12 5:35 ` [RFC PATCH v7 04/37] bpf tools: Open eBPF object file and do basic validation Wang Nan
2015-06-12 5:35 ` [RFC PATCH v7 05/37] bpf tools: Read eBPF object from buffer Wang Nan
2015-06-12 5:35 ` [RFC PATCH v7 06/37] bpf tools: Check endianess and make libbpf fail early Wang Nan
2015-06-12 5:35 ` [RFC PATCH v7 07/37] bpf tools: Iterate over ELF sections to collect information Wang Nan
2015-06-12 5:35 ` [RFC PATCH v7 08/37] bpf tools: Collect version and license from ELF sections Wang Nan
2015-06-12 5:35 ` [RFC PATCH v7 09/37] bpf tools: Collect map definitions from 'maps' section Wang Nan
2015-06-12 5:35 ` [RFC PATCH v7 10/37] bpf tools: Collect symbol table from SHT_SYMTAB section Wang Nan
2015-06-12 5:35 ` [RFC PATCH v7 11/37] bpf tools: Collect eBPF programs from their own sections Wang Nan
2015-06-12 5:35 ` [RFC PATCH v7 12/37] bpf tools: Collect relocation sections from SHT_REL sections Wang Nan
2015-06-12 5:35 ` [RFC PATCH v7 13/37] bpf tools: Record map accessing instructions for each program Wang Nan
2015-06-12 5:35 ` [RFC PATCH v7 14/37] bpf tools: Add bpf.c/h for common bpf operations Wang Nan
2015-06-12 5:35 ` [RFC PATCH v7 15/37] bpf tools: Create eBPF maps defined in an object file Wang Nan
2015-06-12 5:35 ` [RFC PATCH v7 16/37] bpf tools: Relocate eBPF programs Wang Nan
2015-06-12 5:35 ` [RFC PATCH v7 17/37] bpf tools: Introduce bpf_load_program() to bpf.c Wang Nan
2015-06-12 5:35 ` [RFC PATCH v7 18/37] bpf tools: Load eBPF programs in object files into kernel Wang Nan
2015-06-12 5:35 ` [RFC PATCH v7 19/37] bpf tools: Introduce accessors for struct bpf_program Wang Nan
2015-06-12 5:35 ` [RFC PATCH v7 20/37] bpf tools: Introduce accessors for struct bpf_object Wang Nan
2015-06-12 5:35 ` [RFC PATCH v7 21/37] bpf tools: Link all bpf objects onto a list Wang Nan
2015-06-12 5:35 ` [RFC PATCH v7 22/37] perf tools: Make perf depend on libbpf Wang Nan
2015-06-12 5:35 ` [RFC PATCH v7 23/37] perf tools: Introduce llvm config options Wang Nan
2015-06-13 2:31 ` Alexei Starovoitov
2015-06-13 2:52 ` pi3orama
2015-06-13 3:03 ` Alexei Starovoitov
2015-06-13 3:31 ` pi3orama
2015-06-13 4:11 ` pi3orama
2015-06-13 4:43 ` Alexei Starovoitov
2015-06-12 5:35 ` [RFC PATCH v7 24/37] perf tools: Call clang to compile C source to object code Wang Nan
2015-06-12 5:35 ` [RFC PATCH v7 25/37] perf tests: Add LLVM test for eBPF on-the-fly compiling Wang Nan
2015-06-12 5:35 ` [RFC PATCH v7 26/37] perf tools: Auto detecting kernel build directory Wang Nan
2015-06-12 5:35 ` [RFC PATCH v7 27/37] perf tools: Auto detecting kernel include options Wang Nan
2015-06-12 5:35 ` [RFC PATCH v7 28/37] perf record: Enable passing bpf object file to --event Wang Nan
2015-06-12 5:35 ` [RFC PATCH v7 29/37] perf record: Compile scriptlets if pass '.c' " Wang Nan
2015-06-12 5:35 ` [RFC PATCH v7 30/37] perf tools: Parse probe points of eBPF programs during preparation Wang Nan
2015-06-12 5:35 ` [RFC PATCH v7 31/37] perf probe: Attach trace_probe_event with perf_probe_event Wang Nan
2015-06-12 5:35 ` [RFC PATCH v7 32/37] perf record: Probe at kprobe points Wang Nan
2015-06-12 5:35 ` [RFC PATCH v7 33/37] perf record: Load all eBPF object into kernel Wang Nan
2015-06-12 5:35 ` [RFC PATCH v7 34/37] perf tools: Add bpf_fd field to evsel and config it Wang Nan
2015-06-12 5:35 ` [RFC PATCH v7 35/37] perf tools: Attach eBPF program to perf event Wang Nan
2015-06-12 5:35 ` [RFC PATCH v7 36/37] perf tools: Suppress probing messages when probing by BPF loading Wang Nan
2015-06-12 5:35 ` [RFC PATCH v7 37/37] perf record: Add clang options for compiling BPF scripts Wang Nan
2015-06-12 6:08 ` Wangnan (F)
2015-06-12 6:29 ` [RFC PATCH v7 37/37 -fix] " Wang Nan
2015-06-12 16:58 ` Alexei Starovoitov [this message]
2015-06-16 5:22 ` [RFC PATCH v7 00/37] perf tools: filtering events using eBPF programs Wangnan (F)
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=557B0FB4.6000506@plumgrid.com \
--to=ast@plumgrid.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=brendan.d.gregg@gmail.com \
--cc=daniel@iogearbox.net \
--cc=dsahern@gmail.com \
--cc=hekuang@huawei.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=paulus@samba.org \
--cc=pi3orama@163.com \
--cc=wangnan0@huawei.com \
--cc=xiakaixu@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