From: Jiri Olsa <olsajiri@gmail.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Jiri Olsa <jolsa@kernel.org>, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
linux-perf-users@vger.kernel.org, netdev@vger.kernel.org,
bpf@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Martin KaFai Lau <kafai@fb.com>, Song Liu <songliubraving@fb.com>,
Yonghong Song <yhs@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
Ian Rogers <irogers@google.com>
Subject: Re: [PATCH perf/core 3/5] perf tools: Move libbpf init in libbpf_init function
Date: Mon, 25 Apr 2022 09:25:06 +0200 [thread overview]
Message-ID: <YmZM0kd7uWqPOu0x@krava> (raw)
In-Reply-To: <YmLf3PQ9ws2C/Myu@kernel.org>
On Fri, Apr 22, 2022 at 02:03:24PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Fri, Apr 22, 2022 at 12:00:23PM +0200, Jiri Olsa escreveu:
> > Moving the libbpf init code into single function,
> > so we have single place doing that.
>
> Cherry picked this one, waiting for Andrii to chime in wrt the libbpf
> changes, if its acceptable, how to proceed, i.e. in what tree to carry
> these?
I think at this point it's ok with either yours perf/core or bpf-next/master,
I waited for them to be in sync for this ;-)
but as you pointed out there's issue with perf linked with dynamic libbpf,
because the current version does not have the libbpf_register_prog_handler
api that perf needs now.. also it needs the fix and api introduced in this
patchset
I'll check and perhaps we can temporirly disable perf/bpf prologue generation
for dynamic linking..? until the libbpf release has all the needed changes
jirka
>
> - Arnaldo
>
> > Signed-off-by: Jiri Olsa <jolsa@kernel.org>
> > ---
> > tools/perf/util/bpf-loader.c | 27 ++++++++++++++++++---------
> > 1 file changed, 18 insertions(+), 9 deletions(-)
> >
> > diff --git a/tools/perf/util/bpf-loader.c b/tools/perf/util/bpf-loader.c
> > index b72cef1ae959..f8ad581ea247 100644
> > --- a/tools/perf/util/bpf-loader.c
> > +++ b/tools/perf/util/bpf-loader.c
> > @@ -99,16 +99,26 @@ static int bpf_perf_object__add(struct bpf_object *obj)
> > return perf_obj ? 0 : -ENOMEM;
> > }
> >
> > +static int libbpf_init(void)
> > +{
> > + if (libbpf_initialized)
> > + return 0;
> > +
> > + libbpf_set_print(libbpf_perf_print);
> > + libbpf_initialized = true;
> > + return 0;
> > +}
> > +
> > struct bpf_object *
> > bpf__prepare_load_buffer(void *obj_buf, size_t obj_buf_sz, const char *name)
> > {
> > LIBBPF_OPTS(bpf_object_open_opts, opts, .object_name = name);
> > struct bpf_object *obj;
> > + int err;
> >
> > - if (!libbpf_initialized) {
> > - libbpf_set_print(libbpf_perf_print);
> > - libbpf_initialized = true;
> > - }
> > + err = libbpf_init();
> > + if (err)
> > + return ERR_PTR(err);
> >
> > obj = bpf_object__open_mem(obj_buf, obj_buf_sz, &opts);
> > if (IS_ERR_OR_NULL(obj)) {
> > @@ -135,14 +145,13 @@ struct bpf_object *bpf__prepare_load(const char *filename, bool source)
> > {
> > LIBBPF_OPTS(bpf_object_open_opts, opts, .object_name = filename);
> > struct bpf_object *obj;
> > + int err;
> >
> > - if (!libbpf_initialized) {
> > - libbpf_set_print(libbpf_perf_print);
> > - libbpf_initialized = true;
> > - }
> > + err = libbpf_init();
> > + if (err)
> > + return ERR_PTR(err);
> >
> > if (source) {
> > - int err;
> > void *obj_buf;
> > size_t obj_buf_sz;
> >
> > --
> > 2.35.1
>
> --
>
> - Arnaldo
next prev parent reply other threads:[~2022-04-25 7:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 10:00 [PATCH perf/core 0/5] perf tools: Fix prologue generation Jiri Olsa
2022-04-22 10:00 ` [PATCH perf/core 1/5] libbpf: Add bpf_program__set_insns function Jiri Olsa
2022-04-25 16:22 ` Daniel Borkmann
2022-04-26 6:19 ` Jiri Olsa
2022-04-26 6:19 ` Andrii Nakryiko
2022-04-26 6:57 ` Jiri Olsa
2022-04-26 15:58 ` Andrii Nakryiko
2022-04-27 8:42 ` Jiri Olsa
2022-04-27 18:47 ` Andrii Nakryiko
2022-04-22 10:00 ` [PATCH perf/core 2/5] libbpf: Load prog's instructions after prog_prepare_load_fn callback Jiri Olsa
2022-04-22 10:00 ` [PATCH perf/core 3/5] perf tools: Move libbpf init in libbpf_init function Jiri Olsa
2022-04-22 17:03 ` Arnaldo Carvalho de Melo
2022-04-25 7:25 ` Jiri Olsa [this message]
2022-04-26 6:21 ` Andrii Nakryiko
2022-04-22 10:00 ` [PATCH perf/core 4/5] perf tools: Register perfkprobe libbpf section handler Jiri Olsa
2022-04-26 6:22 ` Andrii Nakryiko
2022-04-26 6:58 ` Jiri Olsa
2022-04-22 10:00 ` [PATCH perf/core 5/5] perf tools: Rework prologue generation code Jiri Olsa
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=YmZM0kd7uWqPOu0x@krava \
--to=olsajiri@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=irogers@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kafai@fb.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=yhs@fb.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).