From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: Jiri Olsa <jolsa@kernel.org>, lkml <linux-kernel@vger.kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Namhyung Kim <namhyung@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Ian Rogers <irogers@google.com>,
"linux-perf-use." <linux-perf-users@vger.kernel.org>,
bpf <bpf@vger.kernel.org>, Andrii Nakryiko <andrii@kernel.org>
Subject: Re: [PATCHv3 0/2] perf/bpf: Replace deprecated code
Date: Sat, 5 Mar 2022 16:13:09 -0300 [thread overview]
Message-ID: <YiO2RXfZU0oaKRnd@kernel.org> (raw)
In-Reply-To: <CAEf4BzYZ5adRWP7AtnwDEa51UArjgWvBCF0d+tvoVgv+QSv2cA@mail.gmail.com>
Em Mon, Feb 28, 2022 at 05:49:55PM -0800, Andrii Nakryiko escreveu:
> On Thu, Feb 24, 2022 at 7:52 AM Jiri Olsa <jolsa@kernel.org> wrote:
> >
> > hi,
> > the original patchset [1] removed the whole perf functionality
> > with the hope nobody's using that. But it turned out there's
> > actually bpf script using prologue functionality, so there
> > might be users of this.
> >
> > v3 changes:
> > - sending priv related changes, because they can be already
> > merged, the rest will need more discussion and work
> >
> > - this version gets rid of and adds workaround (and keeps the
> > current functionality) for following deprecated libbpf functions:
> >
> > bpf_program__set_priv
> > bpf_program__priv
> > bpf_map__set_priv
> > bpf_map__priv
> >
> > Basically it implements workarounds suggested by Andrii in [2].
> >
>
> LGTM, for the series:
>
> Acked-by: Andrii Nakryiko <andrii@kernel.org>
Thanks, applied.
- Arnaldo
> > Also available in here:
> > git://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git
> > bpf/depre
> >
> > thanks,
> > jirka
> >
> >
> > [1] https://lore.kernel.org/linux-perf-users/YgoPxhE3OEEmZqla@krava/T/#t
> > [2] https://lore.kernel.org/linux-perf-users/YgoPxhE3OEEmZqla@krava/T/#md3ccab9fe70a4583e94603b1a562e369bd67b17d
> > ---
> > Jiri Olsa (2):
> > perf tools: Remove bpf_program__set_priv/bpf_program__priv usage
> > perf tools: Remove bpf_map__set_priv/bpf_map__priv usage
> >
> > tools/perf/util/bpf-loader.c | 164 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-----------------
> > 1 file changed, 141 insertions(+), 23 deletions(-)
--
- Arnaldo
prev parent reply other threads:[~2022-03-05 19:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 15:52 [PATCHv3 0/2] perf/bpf: Replace deprecated code Jiri Olsa
2022-02-24 15:52 ` [PATCH 1/2] perf tools: Remove bpf_program__set_priv/bpf_program__priv usage Jiri Olsa
2022-02-24 15:52 ` [PATCH 2/2] perf tools: Remove bpf_map__set_priv/bpf_map__priv usage Jiri Olsa
2022-03-01 1:49 ` Andrii Nakryiko
2022-03-01 8:49 ` Jiri Olsa
2022-03-01 1:49 ` [PATCHv3 0/2] perf/bpf: Replace deprecated code Andrii Nakryiko
2022-03-05 19:13 ` 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=YiO2RXfZU0oaKRnd@kernel.org \
--to=acme@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=alexander.shishkin@linux.intel.com \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=namhyung@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 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).