From: Namhyung Kim <namhyung@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
James Clark <james.clark@linaro.org>,
Jiri Olsa <jolsa@kernel.org>,
Kan Liang <kan.liang@linux.intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org, bpf@vger.kernel.org,
linux-trace-devel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
Quentin Monnet <qmo@kernel.org>
Subject: Re: [PATCH 1/1 next] tools build: Remove the libunwind feature tests from the ones detected when test-all.o builds
Date: Mon, 17 Mar 2025 10:06:51 -0700 [thread overview]
Message-ID: <Z9hWqwvNQO0GqH09@google.com> (raw)
In-Reply-To: <CAP-5=fWqpcwc021enM8uMChSgCRB+UW_6z7+=pdsQG9msLJsbw@mail.gmail.com>
Hello,
On Mon, Mar 17, 2025 at 09:10:29AM -0700, Ian Rogers wrote:
> On Wed, Dec 11, 2024 at 7:45 AM Arnaldo Carvalho de Melo
> <acme@kernel.org> wrote:
> >
> > We have a tools/build/feature/test-all.c that has the most common set of
> > features that perf uses and are expected to have its development files
> > available when building perf.
> >
> > When we made libwunwind opt-in we forgot to remove them from the list of
> > features that are assumed to be available when test-all.c builds, remove
> > them.
> >
> > Before this patch:
> >
> > $ rm -rf /tmp/b ; mkdir /tmp/b ; make -C tools/perf O=/tmp/b feature-dump ; grep feature-libunwind-aarch64= /tmp/b/FEATURE-DUMP
> > feature-libunwind-aarch64=1
> > $
> >
> > Even tho this not being test built and those header files being
> > available:
> >
> > $ head -5 tools/build/feature/test-libunwind-aarch64.c
> > // SPDX-License-Identifier: GPL-2.0
> > #include <libunwind-aarch64.h>
> > #include <stdlib.h>
> >
> > extern int UNW_OBJ(dwarf_search_unwind_table) (unw_addr_space_t as,
> > $
> >
> > After this patch:
> >
> > $ grep feature-libunwind- /tmp/b/FEATURE-DUMP
> > $
> >
> > Now an audit on what is being enabled when test-all.c builds will be
> > performed.
> >
> > Fixes: 176c9d1e6a06f2fa ("tools features: Don't check for libunwind devel files by default")
> > Cc: Adrian Hunter <adrian.hunter@intel.com>
> > Cc: Ian Rogers <irogers@google.com>
> > Cc: James Clark <james.clark@linaro.org>
> > Cc: Jiri Olsa <jolsa@kernel.org>
> > Cc: Kan Liang <kan.liang@linux.intel.com>
> > Cc: Namhyung Kim <namhyung@kernel.org>
> > Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
>
> Sorry for the delay on this.
>
> Reviewed-by: Ian Rogers <irogers@google.com>
Thanks for the review, but I think this part is used by other tools like
BPF and tracing. It'd be nice to get reviews from them.
Thanks,
Namhyung
>
> > ---
> > tools/build/Makefile.feature | 7 -------
> > 1 file changed, 7 deletions(-)
> >
> > diff --git a/tools/build/Makefile.feature b/tools/build/Makefile.feature
> > index b2884bc23775e986..9cde51104c2d70ec 100644
> > --- a/tools/build/Makefile.feature
> > +++ b/tools/build/Makefile.feature
> > @@ -90,13 +90,6 @@ FEATURE_TESTS_EXTRA := \
> > libbfd-liberty \
> > libbfd-liberty-z \
> > libopencsd \
> > - libunwind-x86 \
> > - libunwind-x86_64 \
> > - libunwind-arm \
> > - libunwind-aarch64 \
> > - libunwind-debug-frame \
> > - libunwind-debug-frame-arm \
> > - libunwind-debug-frame-aarch64 \
> > cxx \
> > llvm \
> > clang \
> > --
> > 2.47.0
> >
next parent reply other threads:[~2025-03-17 17:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Z1mzpfAUi8zeiFOp@x1>
[not found] ` <CAP-5=fWqpcwc021enM8uMChSgCRB+UW_6z7+=pdsQG9msLJsbw@mail.gmail.com>
2025-03-17 17:06 ` Namhyung Kim [this message]
2025-03-17 17:16 ` [PATCH 1/1 next] tools build: Remove the libunwind feature tests from the ones detected when test-all.o builds Ian Rogers
2025-03-17 21:19 ` Quentin Monnet
2025-03-18 23:51 ` Namhyung Kim
2025-03-19 9:47 ` Jiri Olsa
2025-03-19 22:13 ` Namhyung Kim
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=Z9hWqwvNQO0GqH09@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=bpf@vger.kernel.org \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=qmo@kernel.org \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).