From: Qais Yousef <qais.yousef@arm.com>
To: netdev@vger.kernel.org, bpf@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Steven Rostedt <rostedt@goodmis.org>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
linux-kernel@vger.kernel.org, Qais Yousef <qais.yousef@arm.com>
Subject: [PATCH bpf-next 0/2] Allow attaching to bare tracepoints
Date: Mon, 11 Jan 2021 18:20:25 +0000 [thread overview]
Message-ID: <20210111182027.1448538-1-qais.yousef@arm.com> (raw)
Add some missing glue logic to teach bpf about bare tracepoints - tracepoints
without any trace event associated with them.
Bare tracepoints are declare with DECLARE_TRACE(). Full tracepoints are declare
with TRACE_EVENT().
BPF can attach to these tracepoints as RAW_TRACEPOINT() only as there's no
events in tracefs created with them.
Qais Yousef (2):
trace: bpf: Allow bpf to attach to bare tracepoints
selftests: bpf: Add a new test for bare tracepoints
Documentation/bpf/bpf_design_QA.rst | 6 ++++++
include/trace/bpf_probe.h | 12 ++++++++++--
.../selftests/bpf/bpf_testmod/bpf_testmod-events.h | 6 ++++++
.../testing/selftests/bpf/bpf_testmod/bpf_testmod.c | 2 ++
.../testing/selftests/bpf/prog_tests/module_attach.c | 1 +
.../testing/selftests/bpf/progs/test_module_attach.c | 10 ++++++++++
6 files changed, 35 insertions(+), 2 deletions(-)
--
2.25.1
next reply other threads:[~2021-01-11 18:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 18:20 Qais Yousef [this message]
2021-01-11 18:20 ` [PATCH bpf-next 1/2] trace: bpf: Allow bpf to attach to bare tracepoints Qais Yousef
2021-01-12 20:19 ` Yonghong Song
2021-01-13 10:16 ` Qais Yousef
2021-01-13 16:06 ` Yonghong Song
2021-01-14 2:59 ` kernel test robot
2021-01-14 3:46 ` kernel test robot
2021-01-11 18:20 ` [PATCH bpf-next 2/2] selftests: bpf: Add a new test for " Qais Yousef
2021-01-12 7:26 ` Andrii Nakryiko
2021-01-12 19:27 ` Qais Yousef
2021-01-12 20:07 ` Andrii Nakryiko
2021-01-13 10:21 ` Qais Yousef
2021-01-13 16:40 ` Jean-Philippe Brucker
2021-01-14 12:58 ` Qais Yousef
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=20210111182027.1448538-1-qais.yousef@arm.com \
--to=qais.yousef@arm.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).