From: Martin Lau <kafai@fb.com>
To: Alexei Starovoitov <ast@kernel.org>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
"daniel@iogearbox.net" <daniel@iogearbox.net>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
"x86@kernel.org" <x86@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"bpf@vger.kernel.org" <bpf@vger.kernel.org>,
"Kernel Team" <Kernel-team@fb.com>
Subject: Re: [PATCH bpf 0/3] bpf: Make BPF trampoline friendly to ftrace
Date: Mon, 9 Dec 2019 18:42:25 +0000 [thread overview]
Message-ID: <20191209184221.loxqkxlagbmpr5km@kafai-mbp> (raw)
In-Reply-To: <20191209000114.1876138-1-ast@kernel.org>
On Sun, Dec 08, 2019 at 04:01:11PM -0800, Alexei Starovoitov wrote:
> 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
Acked-by: Martin KaFai Lau <kafai@fb.com>
prev parent reply other threads:[~2019-12-09 18:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 0:01 [PATCH bpf 0/3] bpf: Make BPF trampoline friendly to ftrace Alexei Starovoitov
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 ` Martin Lau [this message]
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=20191209184221.loxqkxlagbmpr5km@kafai-mbp \
--to=kafai@fb.com \
--cc=Kernel-team@fb.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).