From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Wang Nan <wangnan0@huawei.com>
Cc: linux-kernel@vger.kernel.org, pi3orama@163.com, lizefan@huawei.com
Subject: Re: [GIT PULL 00/22] perf tools: filtering events using eBPF programs
Date: Thu, 8 Oct 2015 10:45:46 -0300 [thread overview]
Message-ID: <20151008134546.GB12976@redhat.com> (raw)
In-Reply-To: <1444292984-13135-1-git-send-email-wangnan0@huawei.com>
Em Thu, Oct 08, 2015 at 08:29:22AM +0000, Wang Nan escreveu:
> Hi Arnaldo,
>
> Have we made any progress on this patch set?
Well, only one of the patches, not strictly related to eBPF gave me some
work:
commit 266fa2b22294909ddf6e7d2f8acfe07adf9fd978
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
Date: Thu Sep 24 11:24:18 2015 -0300
perf probe: Use existing routine to look for a kernel module by
dso->short_name
And some patches came from Masami that I think were somehow related to
things you reported, had to review/test/apply/push those as well.
- Arnaldo
> I have finished my vacation. In this new pull request, I rebase BPF patches
> onto the newest perf/core, and fix a document problem in Makefile.perf.
>
> The following changes since commit ae938802443732e77d01f8d5b52b900b9327ff30:
>
> perf python: Support the PERF_RECORD_SWITCH event (2015-10-07 19:41:50 -0300)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/pi3orama/linux tags/perf-ebpf-for-acme-20151008
>
> for you to fetch changes up to 60d6b3bceb3d87497c542dec61e4a968d9e2b488:
>
> perf test: Test BPF prologue (2015-10-08 07:23:33 +0000)
>
> ----------------------------------------------------------------
> EBPF support for perf
>
> - Rebase to newest perf/core
>
> - Fix a document problem in Makefile.perf: NO_BPF -> NO_LIBBPF
>
> Signed-off-by: Wang Nan <wangnan0@huawei.com>
>
> ----------------------------------------------------------------
> He Kuang (2):
> perf tools: Add prologue for BPF programs for fetching arguments
> perf record: Support custom vmlinux path
>
> Wang Nan (20):
> perf tools: Make perf depend on libbpf
> perf ebpf: Add the libbpf glue
> perf tools: Enable passing bpf object file to --event
> perf record, bpf: Create probe points for BPF programs
> perf record: Load eBPF object into kernel
> perf tools: Collect perf_evsel in BPF object files
> perf tools: Attach eBPF program to perf event
> perf record: Add clang options for compiling BPF scripts
> perf tools: Compile scriptlets to BPF objects when passing '.c' to --event
> perf test: Enforce LLVM test for BPF test
> perf test: Add 'perf test BPF'
> perf probe: Reset args and nargs for probe_trace_event when failure
> bpf tools: Load a program with different instances using preprocessor
> perf tools: Add BPF_PROLOGUE config options for further patches
> perf tools: Compile dwarf-regs.c if CONFIG_BPF_PROLOGUE is on
> perf tools: Generate prologue for BPF programs
> perf tools: Use same BPF program if arguments are identical
> perf tools: Allow BPF program attach to uprobe events
> perf test: Enforce LLVM test, add kbuild test
> perf test: Test BPF prologue
>
> tools/build/Makefile.feature | 6 +-
> tools/lib/bpf/libbpf.c | 143 +++++-
> tools/lib/bpf/libbpf.h | 22 +
> tools/perf/MANIFEST | 3 +
> tools/perf/Makefile.perf | 21 +-
> tools/perf/arch/x86/util/Build | 1 +
> tools/perf/builtin-record.c | 11 +
> tools/perf/config/Makefile | 31 +-
> tools/perf/perf.c | 2 +
> tools/perf/tests/Build | 24 +-
> tools/perf/tests/bpf-script-example.c | 48 ++
> tools/perf/tests/bpf-script-test-kbuild.c | 21 +
> tools/perf/tests/bpf-script-test-prologue.c | 35 ++
> tools/perf/tests/bpf.c | 227 ++++++++++
> tools/perf/tests/builtin-test.c | 10 +
> tools/perf/tests/llvm.c | 210 ++++++++-
> tools/perf/tests/llvm.h | 29 ++
> tools/perf/tests/make | 4 +-
> tools/perf/tests/tests.h | 5 +
> tools/perf/util/Build | 2 +
> tools/perf/util/bpf-loader.c | 677 ++++++++++++++++++++++++++++
> tools/perf/util/bpf-loader.h | 94 ++++
> tools/perf/util/bpf-prologue.c | 443 ++++++++++++++++++
> tools/perf/util/bpf-prologue.h | 34 ++
> tools/perf/util/evsel.c | 17 +
> tools/perf/util/evsel.h | 1 +
> tools/perf/util/parse-events.c | 115 +++++
> tools/perf/util/parse-events.h | 9 +
> tools/perf/util/parse-events.l | 6 +
> tools/perf/util/parse-events.y | 29 +-
> tools/perf/util/probe-finder.c | 4 +
> 31 files changed, 2248 insertions(+), 36 deletions(-)
> create mode 100644 tools/perf/tests/bpf-script-example.c
> create mode 100644 tools/perf/tests/bpf-script-test-kbuild.c
> create mode 100644 tools/perf/tests/bpf-script-test-prologue.c
> create mode 100644 tools/perf/tests/bpf.c
> create mode 100644 tools/perf/tests/llvm.h
> create mode 100644 tools/perf/util/bpf-loader.c
> create mode 100644 tools/perf/util/bpf-loader.h
> create mode 100644 tools/perf/util/bpf-prologue.c
> create mode 100644 tools/perf/util/bpf-prologue.h
>
> --
> 1.8.3.4
next prev parent reply other threads:[~2015-10-08 13:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 8:29 [GIT PULL 00/22] perf tools: filtering events using eBPF programs Wang Nan
2015-10-08 8:29 ` [PATCH 01/22] perf tools: Make perf depend on libbpf Wang Nan
2015-10-08 8:29 ` [PATCH 02/22] perf ebpf: Add the libbpf glue Wang Nan
2015-10-08 8:29 ` [PATCH 03/22] perf tools: Enable passing bpf object file to --event Wang Nan
2015-10-08 8:29 ` [PATCH 04/22] perf record, bpf: Create probe points for BPF programs Wang Nan
2015-10-08 8:29 ` [PATCH 05/22] perf record: Load eBPF object into kernel Wang Nan
2015-10-08 8:29 ` [PATCH 06/22] perf tools: Collect perf_evsel in BPF object files Wang Nan
2015-10-08 8:29 ` [PATCH 07/22] perf tools: Attach eBPF program to perf event Wang Nan
2015-10-08 8:29 ` [PATCH 08/22] perf record: Add clang options for compiling BPF scripts Wang Nan
2015-10-08 8:29 ` [PATCH 09/22] perf tools: Compile scriptlets to BPF objects when passing '.c' to --event Wang Nan
2015-10-08 8:29 ` [PATCH 10/22] perf test: Enforce LLVM test for BPF test Wang Nan
2015-10-08 8:29 ` [PATCH 11/22] perf test: Add 'perf test BPF' Wang Nan
2015-10-08 8:29 ` [PATCH 12/22] perf probe: Reset args and nargs for probe_trace_event when failure Wang Nan
2015-10-08 8:29 ` [PATCH 13/22] bpf tools: Load a program with different instances using preprocessor Wang Nan
2015-10-08 8:29 ` [PATCH 14/22] perf tools: Add BPF_PROLOGUE config options for further patches Wang Nan
2015-10-08 8:29 ` [PATCH 15/22] perf tools: Compile dwarf-regs.c if CONFIG_BPF_PROLOGUE is on Wang Nan
2015-10-08 8:29 ` [PATCH 16/22] perf tools: Add prologue for BPF programs for fetching arguments Wang Nan
2015-10-08 8:29 ` [PATCH 17/22] perf tools: Generate prologue for BPF programs Wang Nan
2015-10-08 8:29 ` [PATCH 18/22] perf tools: Use same BPF program if arguments are identical Wang Nan
2015-10-08 8:29 ` [PATCH 19/22] perf record: Support custom vmlinux path Wang Nan
2015-10-08 8:29 ` [PATCH 20/22] perf tools: Allow BPF program attach to uprobe events Wang Nan
2015-10-08 8:29 ` [PATCH 21/22] perf test: Enforce LLVM test, add kbuild test Wang Nan
2015-10-08 8:29 ` [PATCH 22/22] perf test: Test BPF prologue Wang Nan
2015-10-08 13:45 ` Arnaldo Carvalho de Melo [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-09-23 11:22 [GIT PULL 00/22] perf tools: filtering events using eBPF programs Wang Nan
2015-09-23 13:46 ` 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=20151008134546.GB12976@redhat.com \
--to=acme@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.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 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.