From: Jiri Olsa <olsajiri@gmail.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: 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: [PATCHv2 0/3] perf tools: Fix prologue generation
Date: Wed, 1 Jun 2022 20:11:21 +0200 [thread overview]
Message-ID: <YperyVk8bTVT+s2U@krava> (raw)
In-Reply-To: <YpAmW/BDq4346OaI@kernel.org>
On Thu, May 26, 2022 at 10:16:11PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Tue, May 10, 2022 at 09:46:56AM +0200, Jiri Olsa escreveu:
> > hi,
> > sending change we discussed some time ago [1] to get rid of
> > some deprecated functions we use in perf prologue code.
> >
> > Despite the gloomy discussion I think the final code does
> > not look that bad ;-)
> >
> > This patchset removes following libbpf functions from perf:
> > bpf_program__set_prep
> > bpf_program__nth_fd
> > struct bpf_prog_prep_result
>
> So, the first patch is already in torvalds/master, I tried applying the
> other two patches to my local perf/core, that already is merged with
> torvalds/master and:
>
> [root@quaco ~]# perf test 42
> 42: BPF filter :
> 42.1: Basic BPF filtering : FAILED!
> 42.2: BPF pinning : FAILED!
> 42.3: BPF prologue generation : FAILED!
> [root@quaco ~]#
>
> I'll push my local perf/core to tmp.perf/core and continue tomorrow.
hi,
I just rebased my changes on top of your perf/core and it seems to work:
[root@krava perf]# ./perf test bpf
40: LLVM search and compile :
40.1: Basic BPF llvm compile : Ok
40.3: Compile source for BPF prologue generation : Ok
40.4: Compile source for BPF relocation : Ok
42: BPF filter :
42.1: Basic BPF filtering : Ok
42.2: BPF pinning : Ok
42.3: BPF prologue generation : Ok
is it still a problem?
jirka
next prev parent reply other threads:[~2022-06-01 18:11 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 7:46 [PATCHv2 0/3] perf tools: Fix prologue generation Jiri Olsa
2022-05-10 7:46 ` [PATCHv2 bpf-next 1/3] libbpf: Add bpf_program__set_insns function Jiri Olsa
2022-05-10 7:46 ` [PATCHv2 perf/core 2/3] perf tools: Register fallback libbpf section handler Jiri Olsa
2022-05-10 23:45 ` Andrii Nakryiko
2022-05-11 7:36 ` Jiri Olsa
2022-05-10 7:46 ` [PATCHv2 perf/core 3/3] perf tools: Rework prologue generation code Jiri Olsa
2022-05-10 23:48 ` [PATCHv2 0/3] perf tools: Fix prologue generation Andrii Nakryiko
2022-05-11 7:35 ` Jiri Olsa
2022-05-11 18:22 ` Arnaldo Carvalho de Melo
2022-05-17 22:02 ` Andrii Nakryiko
2022-05-18 4:45 ` Ian Rogers
2022-05-18 9:48 ` Jiri Olsa
2022-05-18 9:46 ` Jiri Olsa
2022-05-19 11:03 ` Jiri Olsa
2022-05-20 21:46 ` Andrii Nakryiko
2022-05-21 17:44 ` Arnaldo Carvalho de Melo
2022-05-23 7:49 ` Jiri Olsa
2022-05-23 22:43 ` Andrii Nakryiko
2022-05-24 8:28 ` Jiri Olsa
2022-06-01 17:39 ` Andrii Nakryiko
2022-06-01 18:09 ` Jiri Olsa
2022-05-11 12:20 ` patchwork-bot+netdevbpf
2022-05-27 1:16 ` Arnaldo Carvalho de Melo
2022-06-01 18:11 ` Jiri Olsa [this message]
2022-06-01 22:21 ` Andrii Nakryiko
2022-06-02 10:08 ` 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=YperyVk8bTVT+s2U@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=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).