From: Andres Freund <andres@anarazel.de>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
Namhyung Kim <namhyung@kernel.org>,
Quentin Monnet <quentin@isovalent.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
bpf@vger.kernel.org
Subject: Re: [perf-tools] Build-error in tools/perf/util/annotate.c with LLVM-14
Date: Sun, 3 Jul 2022 14:31:03 -0700 [thread overview]
Message-ID: <20220703213103.n3oxmdnlyjsdrty4@awork3.anarazel.de> (raw)
In-Reply-To: <CA+icZUXCqzZgdSNyPwM+nmdTdPoZrQm2M=2DgOy7j_YHXQ1T6w@mail.gmail.com>
Hi,
On 2022-07-03 22:40:22 +0200, Sedat Dilek wrote:
> My test-case was to build a Linux v5.19-rc4 plus custom patches
> including your v1 patchset.
> make-line:
>
> /home/dileks/bin/perf stat make V=1 -j4 LLVM=1 LLVM_IAS=1
> PAHOLE=/opt/pahole/bin/pahole LOCALVERSION=-1-amd64-clang
> 14-lto KBUILD_BUILD_HOST=iniza KBUILD_BUILD_USER=sedat.dilek@gmail.com
> KBUILD_BUILD_TIMESTAMP=2022-07-03 bindeb-pkg
> KDEB_PKGVERSION=5.19.0~rc4-1~bookworm+dileks1
> [...]
> Hmmm, it took a bit longer as usual.
I don't think the patches would affect the performance of this workload - I
don't know the kernel build process well, but I don't see why anything in it
would trigger bpf programs to be disassembled? I guess the additional three
feature tests can take a tiny bit of time, but...
Sent out a new version, did add you as a CC.
Greetings,
Andres Freund
prev parent reply other threads:[~2022-07-03 21:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-03 10:57 [perf-tools] Build-error in tools/perf/util/annotate.c with LLVM-14 Sedat Dilek
2022-07-03 11:03 ` Sedat Dilek
2022-07-03 11:06 ` Sedat Dilek
2022-07-03 11:54 ` Sedat Dilek
2022-07-03 13:54 ` Arnaldo Carvalho de Melo
2022-07-03 16:54 ` Andres Freund
2022-07-03 17:46 ` Arnaldo Carvalho de Melo
2022-07-03 20:32 ` Sedat Dilek
2022-07-03 16:51 ` Andres Freund
2022-07-03 20:40 ` Sedat Dilek
2022-07-03 21:31 ` Andres Freund [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=20220703213103.n3oxmdnlyjsdrty4@awork3.anarazel.de \
--to=andres@anarazel.de \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=bpf@vger.kernel.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=quentin@isovalent.com \
--cc=sedat.dilek@gmail.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