From: Quentin Monnet <qmo@kernel.org>
To: Ian Rogers <irogers@google.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Eduard Zingerman <eddyz87@gmail.com>,
Kumar Kartikeya Dwivedi <memxor@gmail.com>,
Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
Jiri Olsa <jolsa@kernel.org>, Nick Terrell <terrelln@fb.com>,
David Sterba <dsterba@suse.com>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev
Cc: linux-perf-users@vger.kernel.org, James Clark <james.clark@linaro.org>
Subject: Re: [PATCH v1] bpftool build: Restrict feature tests during bootstrap compilation
Date: Mon, 1 Jun 2026 09:20:01 +0100 [thread overview]
Message-ID: <1a9884b6-df23-42d9-bb68-1d6c774c0657@kernel.org> (raw)
In-Reply-To: <20260531010750.525160-1-irogers@google.com>
2026-05-30 18:07 UTC-0700 ~ Ian Rogers <irogers@google.com>
> When the perf build executes 'make -C ../bpf/bpftool bootstrap', bpftool's
> Makefile unconditionally evaluated feature checks for llvm, libcap, libbfd,
> and disassembler libraries because the bootstrap target was not exempted.
>
> Since the bootstrap bpftool strictly compiles minimal AST parsing and C
> code generation logic without linking LLVM or disassembler libraries, these
> feature check sub-makes are completely redundant.
>
> Exempt the bootstrap target from non-essential feature tests to eliminate
> unneeded sub-make fork overhead during Kbuild startup.
>
> Tested-by: James Clark <james.clark@linaro.org>
> Assisted-by: Gemini:gemini-3.1-pro-preview
> Signed-off-by: Ian Rogers <irogers@google.com>
Makes sense, thank you Ian!
Acked-by: Quentin Monnet <qmo@kernel.org>
next prev parent reply other threads:[~2026-06-01 8:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-31 1:07 Ian Rogers
2026-06-01 8:20 ` Quentin Monnet [this message]
2026-06-05 21:20 ` patchwork-bot+netdevbpf
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=1a9884b6-df23-42d9-bb68-1d6c774c0657@kernel.org \
--to=qmo@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dsterba@suse.com \
--cc=eddyz87@gmail.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=justinstitt@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=song@kernel.org \
--cc=terrelln@fb.com \
--cc=yonghong.song@linux.dev \
/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
all inboxes | Powered by JetHome®