From: Alexei Starovoitov <ast@kernel.org>
To: <davem@davemloft.net>
Cc: <daniel@iogearbox.net>, <rostedt@goodmis.org>, <x86@kernel.org>,
<netdev@vger.kernel.org>, <bpf@vger.kernel.org>,
<kernel-team@fb.com>
Subject: [PATCH bpf 0/3] bpf: Make BPF trampoline friendly to ftrace
Date: Sun, 8 Dec 2019 16:01:11 -0800 [thread overview]
Message-ID: <20191209000114.1876138-1-ast@kernel.org> (raw)
Patch 1 - fix crash function_graph tracer encounters BPF trampoline
Patch 2 - use register_ftrace_direct() API to attach BPF trampoline
Patch 3 - simple test
Alexei Starovoitov (3):
ftrace: Fix function_graph tracer interaction with BPF trampoline
bpf: Make BPF trampoline use register_ftrace_direct() API
selftests/bpf: test function_graph tracer and bpf trampoline together
arch/x86/kernel/ftrace.c | 14 -----
include/linux/bpf.h | 1 +
include/linux/ftrace.h | 5 ++
kernel/bpf/trampoline.c | 64 ++++++++++++++++++++--
kernel/trace/fgraph.c | 9 +++
kernel/trace/ftrace.c | 19 +++----
tools/testing/selftests/bpf/test_ftrace.sh | 39 +++++++++++++
7 files changed, 119 insertions(+), 32 deletions(-)
create mode 100755 tools/testing/selftests/bpf/test_ftrace.sh
--
2.23.0
next reply other threads:[~2019-12-09 0:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 0:01 Alexei Starovoitov [this message]
2019-12-09 0:01 ` [PATCH bpf 1/3] ftrace: Fix function_graph tracer interaction with BPF trampoline Alexei Starovoitov
2019-12-10 16:19 ` Alexei Starovoitov
2019-12-10 16:30 ` Steven Rostedt
2019-12-10 23:35 ` Steven Rostedt
2019-12-10 23:49 ` Alexei Starovoitov
2019-12-09 0:01 ` [PATCH bpf 2/3] bpf: Make BPF trampoline use register_ftrace_direct() API Alexei Starovoitov
2019-12-09 0:01 ` [PATCH bpf 3/3] selftests/bpf: test function_graph tracer and bpf trampoline together Alexei Starovoitov
2019-12-09 18:42 ` [PATCH bpf 0/3] bpf: Make BPF trampoline friendly to ftrace Martin Lau
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=20191209000114.1876138-1-ast@kernel.org \
--to=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=kernel-team@fb.com \
--cc=netdev@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=x86@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.