All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@scylladb.com>
To: Ian Rogers <irogers@google.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: Infinite recursion in `perf record`
Date: Tue, 17 May 2022 16:23:03 +0300	[thread overview]
Message-ID: <659c01ac-7c99-a50b-b52e-9f565f3892f0@scylladb.com> (raw)
In-Reply-To: <CAP-5=fV0rXit7BqBxghE=zK=ao_GYhwkCbu+GhJZebzhVCxq0g@mail.gmail.com>


On 17/05/2022 01.04, Ian Rogers wrote:
>
>> perf-5.17.6-300.fc36.x86_64
>>
> Hi, could you provide more details of the build? I have a bazel based
> build and weak symbols are a problem for me too. For example, arm and
> arm64 code needs building and linking together on an arm64 build for
> the symbols to work properly - normally we just need 1 arch. There
> have also been issues with constant propagation. I'd prefer if we
> could use #ifdefs where we explicitly say what we expect to happen on
> each architecture. Weak symbols' implicit behavior is troublesome.
> With #ifdefs if things are broken then linking fails, which provides
> useful signal.


I'm not sure what details you want. The full build log is available here 
[1].


[1] 
https://kojipkgs.fedoraproject.org//packages/kernel/5.17.6/300.fc36/data/logs/x86_64/build.log


  reply	other threads:[~2022-05-17 13:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-16 15:22 Infinite recursion in `perf record` Avi Kivity
2022-05-16 22:04 ` Ian Rogers
2022-05-17 13:23   ` Avi Kivity [this message]
2022-05-17 14:52 ` Arnaldo Carvalho de Melo
2022-05-17 14:59   ` Avi Kivity
2022-05-17 21:17     ` Arnaldo Carvalho de Melo

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=659c01ac-7c99-a50b-b52e-9f565f3892f0@scylladb.com \
    --to=avi@scylladb.com \
    --cc=irogers@google.com \
    --cc=linux-perf-users@vger.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 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.