From: Yonghong Song <yhs@fb.com>
To: <peterz@infradead.org>, <rostedt@goodmis.org>, <ast@fb.com>,
<daniel@iogearbox.net>, <kafai@fb.com>, <netdev@vger.kernel.org>
Cc: <kernel-team@fb.com>
Subject: [PATCH net-next 0/2] bpf/tracing: allow user space to query prog array on the same tp
Date: Tue, 28 Nov 2017 23:20:34 -0800 [thread overview]
Message-ID: <20171129072036.467246-1-yhs@fb.com> (raw)
Commit e87c6bc3852b ("bpf: permit multiple bpf attachments
for a single perf event") added support to attach multiple
bpf programs to a single perf event. Given a perf event
(kprobe, uprobe, or kernel tracepoint), the perf ioctl interface
is used to query bpf programs attached to the same trace event.
The same ioctl interface is also used to attach bpf program.
Patch #1 had the core implementation and patch #2 added
a test case in tools bpf selftests suite.
Yonghong Song (2):
bpf/tracing: allow user space to query prog array on the same tp
bpf/tracing: add a bpf test for new ioctl query interface
include/linux/bpf.h | 4 ++
include/uapi/linux/perf_event.h | 6 ++
kernel/bpf/core.c | 24 +++++++
kernel/events/core.c | 3 +
kernel/trace/bpf_trace.c | 23 +++++++
tools/include/uapi/linux/perf_event.h | 6 ++
tools/testing/selftests/bpf/Makefile | 2 +-
tools/testing/selftests/bpf/test_progs.c | 107 +++++++++++++++++++++++++++++++
8 files changed, 174 insertions(+), 1 deletion(-)
--
2.9.5
next reply other threads:[~2017-11-29 7:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 7:20 Yonghong Song [this message]
2017-11-29 7:20 ` [PATCH net-next 1/2] bpf/tracing: allow user space to query prog array on the same tp Yonghong Song
2017-11-30 17:27 ` Daniel Borkmann
2017-11-30 19:12 ` Yonghong Song
2017-11-29 7:20 ` [PATCH net-next 2/2] bpf/tracing: add a bpf test for new ioctl query interface Yonghong Song
2017-11-30 5:32 ` [PATCH net-next 0/2] bpf/tracing: allow user space to query prog array on the same tp Alexei Starovoitov
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=20171129072036.467246-1-yhs@fb.com \
--to=yhs@fb.com \
--cc=ast@fb.com \
--cc=daniel@iogearbox.net \
--cc=kafai@fb.com \
--cc=kernel-team@fb.com \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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