From: Daniel Borkmann <daniel@iogearbox.net>
To: davem@davemloft.net
Cc: ast@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
Daniel Borkmann <daniel@iogearbox.net>
Subject: [PATCH net-next 0/3] BPF tracepoints
Date: Wed, 25 Jan 2017 02:28:15 +0100 [thread overview]
Message-ID: <cover.1485306168.git.daniel@iogearbox.net> (raw)
This set adds tracepoints to BPF for better introspection and
debugging. The first two patches are prerequisite for the actual
third patch that adds the tracepoints. I think the first two are
small and straight forward enough that they could ideally go via
net-next, but I'm also open to other suggestions on how to route
them in case that's not applicable (it would reduce potential
merge conflicts on BPF side, though). For details, please see
individual patches.
Thanks a lot!
Daniel Borkmann (3):
trace: add variant without spacing in trace_print_hex_seq
lib, traceevent: add PRINT_HEX_STR variant
bpf: add initial bpf tracepoints
drivers/net/ethernet/mellanox/mlx4/en_rx.c | 3 +
drivers/net/ethernet/mellanox/mlx5/core/en_rx.c | 12 +-
.../net/ethernet/netronome/nfp/nfp_net_common.c | 15 +-
drivers/net/ethernet/qlogic/qede/qede_fp.c | 4 +
drivers/net/virtio_net.c | 12 +-
include/linux/bpf_trace.h | 7 +
include/linux/trace_events.h | 3 +-
include/trace/events/bpf.h | 347 +++++++++++++++++++++
include/trace/events/xdp.h | 53 ++++
include/trace/trace_events.h | 8 +-
kernel/bpf/core.c | 9 +
kernel/bpf/inode.c | 17 +-
kernel/bpf/syscall.c | 19 +-
kernel/trace/trace_output.c | 7 +-
tools/lib/traceevent/event-parse.c | 34 +-
tools/lib/traceevent/event-parse.h | 1 +
.../perf/util/scripting-engines/trace-event-perl.c | 1 +
.../util/scripting-engines/trace-event-python.c | 1 +
18 files changed, 530 insertions(+), 23 deletions(-)
create mode 100644 include/linux/bpf_trace.h
create mode 100644 include/trace/events/bpf.h
create mode 100644 include/trace/events/xdp.h
--
1.9.3
next reply other threads:[~2017-01-25 1:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 1:28 Daniel Borkmann [this message]
2017-01-25 1:28 ` [PATCH net-next 1/3] trace: add variant without spacing in trace_print_hex_seq Daniel Borkmann
2017-01-26 19:53 ` Arnaldo Carvalho de Melo
2017-01-26 20:40 ` Daniel Borkmann
2017-01-30 20:44 ` Steven Rostedt
2017-02-01 8:10 ` Daniel Borkmann
2017-01-25 1:28 ` [PATCH net-next 2/3] lib, traceevent: add PRINT_HEX_STR variant Daniel Borkmann
2017-01-30 19:01 ` Steven Rostedt
2017-01-25 1:28 ` [PATCH net-next 3/3] bpf: add initial bpf tracepoints Daniel Borkmann
2017-01-25 18:19 ` [PATCH net-next 0/3] BPF tracepoints David Miller
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=cover.1485306168.git.daniel@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@kernel.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.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