From: Sebastiano Miano <sebastiano.miano@polito.it>
To: netdev@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net
Cc: mingo@redhat.com, rostedt@goodmis.org, brouer@redhat.com,
fulvio.risso@polito.it
Subject: [bpf-next PATCH 0/3] Add ID to bpf_map/prog tracepoints
Date: Wed, 18 Apr 2018 17:30:42 +0200 [thread overview]
Message-ID: <152406544226.3465.948692097697975172.stgit@localhost.localdomain> (raw)
The following series:
1) Add ID to both map and prog related tracepoints
2) Add a sample program that shows how to monitor and
filter map related events using their IDs.
---
Sebastiano Miano (3):
bpf: add id to map tracepoint
bpf: add id to prog tracepoint
bpf: add sample program to trace map events
include/trace/events/bpf.h | 44 ++++-
samples/bpf/Makefile | 4
samples/bpf/trace_map_events_kern.c | 217 ++++++++++++++++++++++++
samples/bpf/trace_map_events_user.c | 314 +++++++++++++++++++++++++++++++++++
4 files changed, 569 insertions(+), 10 deletions(-)
create mode 100644 samples/bpf/trace_map_events_kern.c
create mode 100644 samples/bpf/trace_map_events_user.c
next reply other threads:[~2018-04-18 15:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 15:30 Sebastiano Miano [this message]
2018-04-18 15:30 ` [bpf-next PATCH 1/3] bpf: add id to map tracepoint Sebastiano Miano
2018-04-19 9:08 ` Jesper Dangaard Brouer
2018-04-18 15:30 ` [bpf-next PATCH 2/3] bpf: add id to prog tracepoint Sebastiano Miano
2018-04-19 9:10 ` Jesper Dangaard Brouer
2018-04-18 15:30 ` [bpf-next PATCH 3/3] bpf: add sample program to trace map events Sebastiano Miano
2018-04-19 9:20 ` Jesper Dangaard Brouer
2018-04-20 0:27 ` Alexei Starovoitov
2018-04-20 9:47 ` Jesper Dangaard Brouer
2018-04-23 14:08 ` Sebastiano Miano
2018-04-23 20:08 ` Alexei Starovoitov
2018-04-23 20:22 ` Jesper Dangaard Brouer
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=152406544226.3465.948692097697975172.stgit@localhost.localdomain \
--to=sebastiano.miano@polito.it \
--cc=ast@kernel.org \
--cc=brouer@redhat.com \
--cc=daniel@iogearbox.net \
--cc=fulvio.risso@polito.it \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.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