From: Namhyung Kim <namhyung@kernel.org>
To: Sasha Levin <sashal@kernel.org>
Cc: "Nathan Chancellor" <nathan@kernel.org>,
"Nicolas Schier" <nsc@kernel.org>,
linux-kbuild@vger.kernel.org, "Shuah Khan" <shuah@kernel.org>,
linux-kselftest@vger.kernel.org,
"Peter Zijlstra" <peterz@infradead.org>,
"Ingo Molnar" <mingo@redhat.com>,
"Arnaldo Carvalho de Melo" <acme@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Alexander Shishkin" <alexander.shishkin@linux.intel.com>,
"Jiri Olsa" <jolsa@kernel.org>, "Ian Rogers" <irogers@google.com>,
"Adrian Hunter" <adrian.hunter@intel.com>,
"James Clark" <james.clark@linaro.org>,
linux-perf-users@vger.kernel.org,
"Thomas Weißschuh" <linux@weissschuh.net>,
"Andrew Morton" <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v2 4/7] tools: build perf in tools_build
Date: Wed, 21 Oct 2026 16:23:54 -0700 [thread overview]
Message-ID: <atlJij2v6sbOYZot@google.com> (raw)
In-Reply-To: <20261016143143.3613501-5-sashal@kernel.org>
On Fri, Oct 16, 2026 at 10:31:40AM -0400, Sasha Levin wrote:
> Add CONFIG_TOOLS_BUILD_PERF. perf is built as it is built standalone,
> with optional features enabled when their libraries are installed, and
> with perf's WERROR setting following CONFIG_WERROR. The feature table is
> left out of the kernel build log.
>
> CONFIG_TOOLS_BUILD_PERF_MINIMAL builds it with MINIMAL=1 instead, which
> turns every optional feature off, so the result does not depend on the
> build machine. allmodconfig and allyesconfig turn it on.
>
> Assisted-by: LLM
> Signed-off-by: Sasha Levin <sashal@kernel.org>
Acked-by: Namhyung Kim <namhyung@kernel.org>
Thanks,
Namhyung
> ---
> tools/Kconfig | 16 ++++++++++++++++
> tools/Makefile.kbuild | 10 ++++++++++
> 2 files changed, 26 insertions(+)
>
> diff --git a/tools/Kconfig b/tools/Kconfig
> index 2d05c8e593e21..4f13e3b104377 100644
> --- a/tools/Kconfig
> +++ b/tools/Kconfig
> @@ -60,6 +60,22 @@ config TOOLS_BUILD_IIO
> help
> Build tools/iio (lsiio, iio_event_monitor, iio_generic_buffer).
>
> +config TOOLS_BUILD_PERF
> + bool "perf"
> + help
> + Build tools/perf. As in a standalone perf build, optional
> + features are enabled when the libraries they need are installed.
> +
> +config TOOLS_BUILD_PERF_MINIMAL
> + bool "Build perf with all optional features disabled"
> + depends on TOOLS_BUILD_PERF
> + help
> + Build perf with MINIMAL=1, which turns off every optional
> + feature, so that the result does not depend on which libraries
> + the build machine has installed. allmodconfig and allyesconfig
> + turn this on, which keeps their builds the same on every
> + machine.
> +
> config TOOLS_BUILD_SPI
> bool "SPI tools"
> help
> diff --git a/tools/Makefile.kbuild b/tools/Makefile.kbuild
> index 8cfa7f80039cd..4b3ea73bc8ab9 100644
> --- a/tools/Makefile.kbuild
> +++ b/tools/Makefile.kbuild
> @@ -79,6 +79,16 @@ PHONY += $(tool-targets)
> $(tool-targets): tool-%: FORCE
> $(call build,$(outdir)/$*,-C $(toolsdir)/$* O=$(outdir)/$* CC='$(call escsq,$(tools-cc))',,TOOLS_BUILD_$(shell echo $* | tr a-z A-Z))
>
> +# perf, without the feature table in the kernel build log
> +perf-flags := CC='$(call escsq,$(tools-cc))' FEATURE_DISPLAY= WERROR=$(if $(CONFIG_WERROR),1,0)
> +perf-flags-$(CONFIG_TOOLS_BUILD_PERF_MINIMAL) += MINIMAL=1
> +
> +__tools_build: $(if $(CONFIG_TOOLS_BUILD_PERF),perf)
> +
> +PHONY += perf
> +perf: FORCE
> + $(call build,$(outdir)/perf,-C $(toolsdir)/perf -f Makefile.perf O=$(outdir)/perf $(perf-flags) $(perf-flags-y),,TOOLS_BUILD_PERF)
> +
> PHONY += FORCE
> FORCE:
>
> --
> 2.53.0
>
next prev parent reply other threads:[~2026-10-21 23:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 14:31 [RFC PATCH v2 0/7] kbuild: build the userspace tools in tools/ with the kernel Sasha Levin
2026-10-16 14:31 ` [RFC PATCH v2 1/7] kbuild: factor the userspace ABI flags out into KBUILD_USERABI Sasha Levin
[not found] ` <sashiko-outbox-175552@kernel.org>
2026-10-18 14:39 ` Sasha Levin
2026-10-16 14:31 ` [RFC PATCH v2 2/7] kbuild: add "make tools_build" to build userspace tools from tools/ Sasha Levin
[not found] ` <sashiko-outbox-175553@kernel.org>
2026-10-18 14:39 ` Sasha Levin
2026-10-16 14:31 ` [RFC PATCH v2 3/7] perf build: Add MINIMAL=1 to build without optional features Sasha Levin
2026-10-16 15:41 ` Ian Rogers
2026-10-18 13:53 ` Sasha Levin
2026-10-21 23:23 ` Namhyung Kim
2026-10-16 14:31 ` [RFC PATCH v2 4/7] tools: build perf in tools_build Sasha Levin
2026-10-21 23:23 ` Namhyung Kim [this message]
2026-10-16 14:31 ` [RFC PATCH v2 5/7] tools: build kernel selftests " Sasha Levin
2026-10-16 16:17 ` Shuah Khan
[not found] ` <sashiko-outbox-175556@kernel.org>
2026-10-18 14:39 ` Sasha Levin
2026-10-16 14:31 ` [RFC PATCH v2 6/7] kbuild: build the tools selected in tools/Kconfig as part of "make all" Sasha Levin
2026-10-16 14:31 ` [RFC PATCH v2 7/7] Documentation: describe building tools with the kernel Sasha Levin
2026-10-20 11:52 ` [RFC PATCH v2 0/7] kbuild: build the userspace tools in tools/ " Thorsten Leemhuis
2026-10-20 12:43 ` Sasha Levin
2026-10-20 13:14 ` Thorsten Leemhuis
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=atlJij2v6sbOYZot@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=nathan@kernel.org \
--cc=nsc@kernel.org \
--cc=peterz@infradead.org \
--cc=sashal@kernel.org \
--cc=shuah@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 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®