From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Tomas Glozar <tglozar@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Gabriele Monaco <gmonaco@redhat.com>,
James Clark <james.clark@linaro.org>,
Jiri Olsa <jolsa@kernel.org>,
Kan Liang <kan.liang@linux.intel.com>,
Steven Rostedt <rostedt@goodmis.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH 1/1] tools build: Don't assume libtracefs-devel is always available
Date: Thu, 2 Oct 2025 12:46:45 -0300 [thread overview]
Message-ID: <aN6eZby8fc8PyClB@x1> (raw)
In-Reply-To: <CAP-5=fUfBzUTOJG7t7nwvZkcf+LKVakGnNqgVLSW8CjsLxFkDw@mail.gmail.com>
On Thu, Oct 02, 2025 at 08:21:08AM -0700, Ian Rogers wrote:
> On Thu, Oct 2, 2025 at 7:13 AM Tomas Glozar <tglozar@redhat.com> wrote:
> >
> > čt 2. 10. 2025 v 15:05 odesílatel Arnaldo Carvalho de Melo
> > <acme@kernel.org> napsal:
> > >
> > > perf doesn't use libtracefs and so it doesn't make sense to assume it is
> > > always available when building test-all.bin, defeating the feature check
> > > speedup it provides.
> > >
> > > The other tools/build/ users such as rtla, rv, etc call $(feature_check
> > > libtracefs) to check its availability instead of using the test-all.bin
> > > mechanism, stopping the build and asking for libtracefs-devel to be
> > > installed.
> > >
> > > Noticed after applying Ian Roger's removal unused libtracefs
> > > configuration in tools/perf/.
> > >
> > > Cc: Adrian Hunter <adrian.hunter@intel.com>
> > > Cc: Gabriele Monaco <gmonaco@redhat.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>
> > > Cc: Steven Rostedt <rostedt@goodmis.org>
> > > Cc: Tomas Glozar <tglozar@redhat.com>
> > > Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
> >
> > Acked-by: Tomas Glozar <tglozar@redhat.com>
> >
> > Perhaps it would also make sense to clarify in a comment that
> > test-all.c is to speed up perf build rather than rv, rtla etc. (which
> > don't use most of the dependencies listed there)?
>
> There's a big comment in Makefile.feature:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/build/Makefile.feature#n24
> I think that FEATURE_TESTS_BASIC tests are covered by test-all.c so I
> think this change needs to remove libtracefs from FEATURE_TESTS_BASIC
> otherwise $(feature-libtracefs) will evaluate to 1 even though no
> libtracefs testing has been performed.
Done, thanks for catching this.
> We can't just remove the tracefs feature test as there are
> dependencies in rv, rtla, etc.
And those, as noted, don't rely on test-all.bin to detect the presence
of libtracefs:
⬢ [acme@toolbx perf-tools-next]$ git grep feature.*libtracefs tools/
tools/tracing/latency/Makefile.config:$(call feature_check,libtracefs)
tools/tracing/latency/Makefile.config:ifeq ($(feature-libtracefs), 1)
tools/tracing/rtla/Makefile.config:$(call feature_check,libtracefs)
tools/tracing/rtla/Makefile.config:ifeq ($(feature-libtracefs), 1)
tools/verification/rv/Makefile.config:$(call feature_check,libtracefs)
tools/verification/rv/Makefile.config:ifeq ($(feature-libtracefs), 1)
⬢ [acme@toolbx perf-tools-next]$
Can I have your Reviewed-by or Acked-by?
Thanks,
- Arnaldo
prev parent reply other threads:[~2025-10-02 15:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 13:05 [PATCH 1/1] tools build: Don't assume libtracefs-devel is always available Arnaldo Carvalho de Melo
2025-10-02 14:13 ` Tomas Glozar
2025-10-02 15:21 ` Ian Rogers
2025-10-02 15:46 ` Arnaldo Carvalho de Melo [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=aN6eZby8fc8PyClB@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=gmonaco@redhat.com \
--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=namhyung@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglozar@redhat.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 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.