From: Christy Lee <christylee@fb.com>
To: <andrii@kernel.org>, <acme@kernel.org>, <jolsa@redhat.com>
Cc: <christylee@fb.com>, <christyc.y.lee@gmail.com>,
<bpf@vger.kernel.org>, <linux-perf-users@vger.kernel.org>,
<kernel-team@fb.com>, <wangnan0@huawei.com>,
<bobo.shaobowang@huawei.com>, <yuehaibing@huawei.com>
Subject: [PATCH bpf-next v2 0/2] perf: stop using deprecated bpf APIs
Date: Thu, 6 Jan 2022 12:00:30 -0800 [thread overview]
Message-ID: <20220106200032.3067127-1-christylee@fb.com> (raw)
libbpf's bpf_prog_load() and bpf__object_next() APIs are deprecated.
remove perf's usage of these deprecated functions. After this patch
set, the only remaining libbpf deprecated APIs in perf would be
bpf_program__set_prep() and bpf_program__nth_fd().
Changelog:
----------
v1 -> v2:
https://lore.kernel.org/all/20211216222108.110518-1-christylee@fb.com/
Patch 1/2:
Added missing commit message
Patch 2/2:
Added more details to commit message and added steps to reproduce
original test case.
Christy Lee (2):
perf: stop using deprecated bpf_prog_load() API
perf: stop using deprecated bpf__object_next() API
tools/perf/tests/bpf.c | 14 ++-----
tools/perf/util/bpf-loader.c | 72 +++++++++++++++++++++++++++---------
tools/perf/util/bpf-loader.h | 1 +
3 files changed, 59 insertions(+), 28 deletions(-)
--
2.30.2
next reply other threads:[~2022-01-06 20:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 20:00 Christy Lee [this message]
2022-01-06 20:00 ` [PATCH bpf-next v2 1/2] perf: stop using deprecated bpf_prog_load() API Christy Lee
2022-01-06 21:24 ` Andrii Nakryiko
2022-01-06 20:00 ` [PATCH bpf-next v2 2/2] perf: stop using deprecated bpf__object_next() API Christy Lee
2022-01-07 3:21 ` Yonghong Song
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=20220106200032.3067127-1-christylee@fb.com \
--to=christylee@fb.com \
--cc=acme@kernel.org \
--cc=andrii@kernel.org \
--cc=bobo.shaobowang@huawei.com \
--cc=bpf@vger.kernel.org \
--cc=christyc.y.lee@gmail.com \
--cc=jolsa@redhat.com \
--cc=kernel-team@fb.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=wangnan0@huawei.com \
--cc=yuehaibing@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.