From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: Jiri Olsa <olsajiri@gmail.com>,
Andrii Nakryiko <andrii@kernel.org>,
"linux-perf-use." <linux-perf-users@vger.kernel.org>,
bpf <bpf@vger.kernel.org>, Christy Lee <christylee@fb.com>,
Jiri Olsa <jolsa@redhat.com>
Subject: Re: [PATCH v6 perf/core 0/2] perf: stop using deprecated bpf APIs
Date: Mon, 14 Feb 2022 15:58:28 -0300 [thread overview]
Message-ID: <YgqmVOhBzkb3EyYh@kernel.org> (raw)
In-Reply-To: <CAEf4Bzav96MoZh08s7UZfnLQPTRbF+UvuWA75r0GPkYTRGdsYg@mail.gmail.com>
Em Sat, Feb 12, 2022 at 05:47:25PM -0800, Andrii Nakryiko escreveu:
> On Sat, Feb 12, 2022 at 10:18 AM Jiri Olsa <olsajiri@gmail.com> wrote:
> >
> > 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
>
> great, thanks for checking!
All tests passed, patches merged and pushed out to perf/core, thanks!
- Arnaldo
> >
> > 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
> > >
--
- Arnaldo
prev parent reply other threads:[~2022-02-14 19:02 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 ` [PATCH v6 perf/core 0/2] perf: stop using deprecated bpf APIs Jiri Olsa
2022-02-13 1:47 ` Andrii Nakryiko
2022-02-14 18:58 ` Arnaldo Carvalho de Melo [this message]
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=YgqmVOhBzkb3EyYh@kernel.org \
--to=acme@kernel.org \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=christylee@fb.com \
--cc=jolsa@redhat.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=olsajiri@gmail.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;
as well as URLs for NNTP newsgroup(s).