From: Kui-Feng Lee <kuifeng@fb.com>
To: <bpf@vger.kernel.org>, <ast@kernel.org>, <daniel@iogearbox.net>,
<andrii@kernel.org>
Cc: Kui-Feng Lee <kuifeng@fb.com>
Subject: [PATCH v4 bpf-next 0/4] Stop using bpf_object__find_program_by_title API
Date: Mon, 10 Jan 2022 14:34:42 -0800 [thread overview]
Message-ID: <20220110223446.345531-1-kuifeng@fb.com> (raw)
bpf_object__find_program_by_title is going to be deprecated since
v0.7. Replace all use cases with bpf_object__find_program_by_name if
possible, or use bpf_object__for_each_program to iterate over
programs, matching section names.
V3 fixes a broken test case, fexit_bpf2bpf, in selftests/bpf, using
bpf_obj__for_each_program API instead.
[v2] https://lore.kernel.org/bpf/20211211003608.2764928-1-kuifeng@fb.com/
[v1] https://lore.kernel.org/bpf/20211210190855.1369060-1-kuifeng@fb.com/T/
Kui-Feng Lee (4):
selftests/bpf: Stop using bpf_object__find_program_by_title API.
samples/bpf: Stop using bpf_object__find_program_by_title API.
tools/perf: Stop using bpf_object__find_program_by_title API.
libbpf: Mark bpf_object__find_program_by_title API deprecated.
samples/bpf/hbm.c | 11 ++-
samples/bpf/xdp_fwd_user.c | 12 ++-
tools/lib/bpf/libbpf.h | 1 +
tools/perf/builtin-trace.c | 13 ++-
.../selftests/bpf/prog_tests/bpf_obj_id.c | 4 +-
.../bpf/prog_tests/connect_force_port.c | 18 ++---
.../selftests/bpf/prog_tests/core_reloc.c | 79 +++++++++++++------
.../selftests/bpf/prog_tests/fexit_bpf2bpf.c | 17 +++-
.../bpf/prog_tests/get_stack_raw_tp.c | 4 +-
.../bpf/prog_tests/sockopt_inherit.c | 15 ++--
.../selftests/bpf/prog_tests/stacktrace_map.c | 4 +-
.../bpf/prog_tests/stacktrace_map_raw_tp.c | 4 +-
.../selftests/bpf/prog_tests/test_overhead.c | 20 ++---
.../bpf/prog_tests/trampoline_count.c | 6 +-
14 files changed, 137 insertions(+), 71 deletions(-)
--
2.30.2
next reply other threads:[~2022-01-10 22:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 22:34 Kui-Feng Lee [this message]
2022-01-10 22:34 ` [PATCH v4 bpf-next 1/4] selftests/bpf: Stop using bpf_object__find_program_by_title API Kui-Feng Lee
2022-01-10 22:34 ` [PATCH v4 bpf-next 2/4] samples/bpf: " Kui-Feng Lee
2022-01-10 22:34 ` [PATCH v4 bpf-next 3/4] tools/perf: " Kui-Feng Lee
2022-01-10 22:45 ` [PATCH v4 bpf-next 0/4] " Kui-Feng Lee
-- strict thread matches above, loose matches on Subject: below --
2021-12-14 3:59 Kui-Feng Lee
2021-12-14 23:10 ` patchwork-bot+netdevbpf
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=20220110223446.345531-1-kuifeng@fb.com \
--to=kuifeng@fb.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
/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