From: Andrii Nakryiko <andrii@kernel.org>
To: <bpf@vger.kernel.org>, <ast@kernel.org>, <daniel@iogearbox.net>
Cc: <andrii@kernel.org>, <kernel-team@fb.com>,
Dave Marchevsky <davemarchevsky@fb.com>
Subject: [PATCH bpf-next 0/3] Revamp and fix libbpf's feature-probing APIs
Date: Wed, 15 Dec 2021 23:04:39 -0800 [thread overview]
Message-ID: <20211216070442.1492204-1-andrii@kernel.org> (raw)
Fix and improve libbpf feature-probing APIs. Name them consistently and
deprecated previous inconsistently named APIs.
Cc: Dave Marchevsky <davemarchevsky@fb.com>
Andrii Nakryiko (3):
libbpf: rework feature-probing APIs
selftests/bpf: add libbpf feature-probing API selftests
bpftool: reimplement large insn size limit feature probing
tools/bpf/bpftool/feature.c | 26 +-
tools/lib/bpf/libbpf.h | 52 +++-
tools/lib/bpf/libbpf.map | 3 +
tools/lib/bpf/libbpf_probes.c | 235 ++++++++++++++----
tools/testing/selftests/bpf/config | 2 +
.../selftests/bpf/prog_tests/libbpf_probes.c | 124 +++++++++
6 files changed, 385 insertions(+), 57 deletions(-)
create mode 100644 tools/testing/selftests/bpf/prog_tests/libbpf_probes.c
--
2.30.2
next reply other threads:[~2021-12-16 7:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 7:04 Andrii Nakryiko [this message]
2021-12-16 7:04 ` [PATCH bpf-next 1/3] libbpf: rework feature-probing APIs Andrii Nakryiko
2021-12-17 0:10 ` Dave Marchevsky
2021-12-17 0:41 ` Andrii Nakryiko
2021-12-17 7:07 ` Dave Marchevsky
2021-12-16 7:04 ` [PATCH bpf-next 2/3] selftests/bpf: add libbpf feature-probing API selftests Andrii Nakryiko
2021-12-17 0:21 ` Dave Marchevsky
2021-12-17 0:42 ` Andrii Nakryiko
2021-12-17 17:09 ` Andrii Nakryiko
2021-12-16 7:04 ` [PATCH bpf-next 3/3] bpftool: reimplement large insn size limit feature probing Andrii Nakryiko
2021-12-17 0:36 ` Dave Marchevsky
-- strict thread matches above, loose matches on Subject: below --
2021-12-16 5:05 [PATCH bpf-next 0/3] Revamp and fix libbpf's feature-probing APIs Andrii Nakryiko
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=20211216070442.1492204-1-andrii@kernel.org \
--to=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davemarchevsky@fb.com \
--cc=kernel-team@fb.com \
/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