From: Jiri Olsa <olsajiri@gmail.com>
To: Andrii Nakryiko <andrii@kernel.org>
Cc: acme@kernel.org, linux-perf-users@vger.kernel.org,
bpf@vger.kernel.org, christylee@fb.com, jolsa@redhat.com
Subject: Re: [PATCH v6 perf/core 0/2] perf: stop using deprecated bpf APIs
Date: Sat, 12 Feb 2022 19:18:16 +0100 [thread overview]
Message-ID: <Ygf56M45VuWfippn@krava> (raw)
In-Reply-To: <20220212155125.3406232-1-andrii@kernel.org>
On Sat, Feb 12, 2022 at 07:51:23AM -0800, Andrii Nakryiko wrote:
> 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().
>
> v5 -> v6:
> - rebase onto perf/core tree (Arnaldo);
looks good, tests are passing for me
jirka
> v4 -> v5:
> - add bpf_perf_object__add() and use it where appropriate (Jiri);
> - use __maybe_unused in first patch;
> v3 -> v4:
> - Fixed commit title
> - Added weak definition for deprecated function
> v2 -> v3:
> - Fixed commit message to use upstream perf
> v1 -> v2:
> - Added missing commit message
> - Added more details to commit message and added steps to reproduce
> original test case.
>
> Christy Lee (2):
> perf: Stop using deprecated bpf_load_program() API
> perf: Stop using deprecated bpf_object__next() API
>
> tools/perf/tests/bpf.c | 14 ++----
> tools/perf/util/bpf-event.c | 13 +++++
> tools/perf/util/bpf-loader.c | 98 +++++++++++++++++++++++++++++-------
> 3 files changed, 96 insertions(+), 29 deletions(-)
>
> --
> 2.30.2
>
next prev parent reply other threads:[~2022-02-12 18:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-12 15:51 [PATCH v6 perf/core 0/2] perf: stop using deprecated bpf APIs Andrii Nakryiko
2022-02-12 15:51 ` [PATCH v6 perf/core 1/2] perf: Stop using deprecated bpf_load_program() API Andrii Nakryiko
2022-02-12 15:51 ` [PATCH v6 perf/core 2/2] perf: Stop using deprecated bpf_object__next() API Andrii Nakryiko
2022-02-12 18:18 ` Jiri Olsa [this message]
2022-02-13 1:47 ` [PATCH v6 perf/core 0/2] perf: stop using deprecated bpf APIs Andrii Nakryiko
2022-02-14 18:58 ` Arnaldo Carvalho de Melo
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=Ygf56M45VuWfippn@krava \
--to=olsajiri@gmail.com \
--cc=acme@kernel.org \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=christylee@fb.com \
--cc=jolsa@redhat.com \
--cc=linux-perf-users@vger.kernel.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 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.