From: Andrey Ignatov <rdna@fb•com>
To: <ast@kernel•org>, <daniel@iogearbox•net>
Cc: Andrey Ignatov <rdna@fb•com>, <kubakici@wp•pl>,
<quentin.monnet@netronome•com>, <netdev@vger•kernel.org>,
<kernel-team@fb•com>
Subject: [PATCH v2 bpf-next 0/3] Add missing types to bpftool, libbpf
Date: Tue, 17 Apr 2018 10:28:43 -0700 [thread overview]
Message-ID: <cover.1523985784.git.rdna@fb.com> (raw)
v1->v2:
- add new types to bpftool-cgroup man page;
- add new types to bash completion for bpftool;
- don't add types that should not be in bpftool cgroup.
Add support for various BPF prog types and attach types that have been
added to kernel recently but not to bpftool or libbpf yet.
Andrey Ignatov (3):
bpftool: Support new prog types and attach types
libbpf: Support guessing post_bind{4,6} progs
libbpf: Type functions for raw tracepoints
tools/bpf/bpftool/Documentation/bpftool-cgroup.rst | 11 +++++++++--
tools/bpf/bpftool/bash-completion/bpftool | 6 ++++--
tools/bpf/bpftool/cgroup.c | 15 ++++++++++++---
tools/bpf/bpftool/prog.c | 3 +++
tools/lib/bpf/libbpf.c | 8 ++++++++
tools/lib/bpf/libbpf.h | 2 ++
6 files changed, 38 insertions(+), 7 deletions(-)
--
2.9.5
next reply other threads:[~2018-04-17 17:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 17:28 Andrey Ignatov [this message]
2018-04-17 17:28 ` [PATCH v2 bpf-next 1/3] bpftool: Support new prog types and attach types Andrey Ignatov
2018-04-17 23:09 ` Jakub Kicinski
2018-04-17 17:28 ` [PATCH v2 bpf-next 2/3] libbpf: Support guessing post_bind{4,6} progs Andrey Ignatov
2018-04-17 17:28 ` [PATCH v2 bpf-next 3/3] libbpf: Type functions for raw tracepoints Andrey Ignatov
2018-04-18 0:58 ` [PATCH v2 bpf-next 0/3] Add missing types to bpftool, libbpf Alexei Starovoitov
2018-04-18 12:42 ` Daniel Borkmann
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.1523985784.git.rdna@fb.com \
--to=rdna@fb$(echo .)com \
--cc=ast@kernel$(echo .)org \
--cc=daniel@iogearbox$(echo .)net \
--cc=kernel-team@fb$(echo .)com \
--cc=kubakici@wp$(echo .)pl \
--cc=netdev@vger$(echo .)kernel.org \
--cc=quentin.monnet@netronome$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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