All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jiri Olsa <olsajiri@gmail.com>
Cc: Thomas Richter <tmricht@linux.ibm.com>,
	"linux-perf-use." <linux-perf-users@vger.kernel.org>,
	Jiri Olsa <jolsa@redhat.com>,
	Sumanth Korikkar <sumanthk@linux.ibm.com>,
	Heiko Carstens <hca@linux.ibm.com>,
	vasily Gorbik <gor@linux.ibm.com>,
	Ian Rogers <irogers@google.com>,
	Ilya Leoshkevich <iii@linux.ibm.com>,
	Sven Schnelle <svens@linux.ibm.com>
Subject: Re: perf test case 40 LLVM search and compile runs endless (eBPF linkage issue)
Date: Tue, 24 May 2022 11:33:35 -0300	[thread overview]
Message-ID: <Yozsvxx0JsTbVgW1@kernel.org> (raw)
In-Reply-To: <YozLKby7ITEtchC9@krava>

Em Tue, May 24, 2022 at 02:10:17PM +0200, Jiri Olsa escreveu:
> On Mon, May 23, 2022 at 01:09:51PM +0200, Jiri Olsa wrote:
> > On Mon, May 23, 2022 at 12:52:06PM +0200, Thomas Richter wrote:
> > > On s390 the test case 40 'LLVM search and compile' runs for ever:
> > > 
> > >   # date; timeout 30s perf test -F 40; date
> > >   Mon May 23 12:35:48 PM CEST 2022
> > >    40: LLVM search and compile   :
> > >    40.1: Basic BPF llvm compile  :
> > >   Mon May 23 12:36:18 PM CEST 2022
> > >   #
> > > 
> > > Investigation by Ilya Leoshkevich revealed:
> > > On s390 we hit an endless loop where bpf_object__next_program and bpf_program__next 
> > > infinitely call each other. We tracked this down to ld.so preferring the perf's 
> > > bpf_object__next_program weak copy over the libbpf's strong one.
> > > 
> > > This is introduced with commit 2a4898fc264a ("perf tools: Add more weak libbpf functions")
> > > 
> > > Also see discussion in 
> > > https://lore.kernel.org/lkml/YY%2FAR2Dcaws0BAE9@kernel.org/
> > > 
> > > How can this be fixed asap? Thanks a lot.
> > 
> > I was just suggesting to remove that:
> >   https://lore.kernel.org/bpf/Yos8hq3NmBwemoJw@krava/T/#mda8abccbf475b99d25abe5498a5df1af2da82ee8
> > 
> > it's no longer needed and can cause problem apparently
> 
> after discussing with Arnaldo we decided to go for another fix,
> could you please try this branch:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git
>   perf/weak

I'm adding comments, testing and applying that series in my local tree,
so far so good, will push to tmp.perf/core later.

Please let us know if you guys looked at the patches in Jiri's perf/weak
branch and if you are ok with it so that I can add
Tested-by/acked-by/reviewed-by, which are always more than welcome.

Thanks,

- Arnaldo

  reply	other threads:[~2022-05-24 14:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-23 10:52 perf test case 40 LLVM search and compile runs endless (eBPF linkage issue) Thomas Richter
2022-05-23 11:09 ` Jiri Olsa
2022-05-24 12:10   ` Jiri Olsa
2022-05-24 14:33     ` Arnaldo Carvalho de Melo [this message]
2022-05-25 14:10       ` Thomas Richter

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=Yozsvxx0JsTbVgW1@kernel.org \
    --to=acme@kernel.org \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=iii@linux.ibm.com \
    --cc=irogers@google.com \
    --cc=jolsa@redhat.com \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=olsajiri@gmail.com \
    --cc=sumanthk@linux.ibm.com \
    --cc=svens@linux.ibm.com \
    --cc=tmricht@linux.ibm.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 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.