From: Daniel Bristot de Oliveira <bristot@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Steven Rostedt <rostedt@goodmis.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Daniel Bristot de Oliveira <bristot@kernel.org>,
Josh Poimboeuf <jpoimboe@kernel.org>,
John Kacur <jkacur@redhat.com>,
Namhyung Kim <namhyung@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
linux-perf-users@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] tools/tracing: Use tools/build makefiles like perf
Date: Fri, 8 Mar 2024 18:50:42 +0100 [thread overview]
Message-ID: <cover.1709914259.git.bristot@kernel.org> (raw)
tools/tracing and tools/verification/rv are using standalone Makefiles.
However, This approach has some drawbacks. For example, code
duplication and lack of proper dependency handling, making things
harder for users.
Linus suggested using perf's build system, and it is indeed the best way to go.
This series replaces tools/tracing and tools/verification/rv makefiles
with makefiles inspired by perf and objtool that use tools/build/
infrastructure.
Thanks, Arnaldo, for the pointers via chat.
Link: https://lore.kernel.org/lkml/CAHk-=wjQ9BJKBPi3sJN2Dy5jVwPO03u9aOc6-g8AnLcGq-E4-g@mail.gmail.com/
Daniel Bristot de Oliveira (3):
tools/tracing: Use tools/build makefiles on latency-collector
tools/verification: Use tools/build makefiles on rv
tools/rtla: Use tools/build makefiles to build rtla
tools/tracing/latency/.gitignore | 1 +
tools/tracing/latency/Build | 1 +
tools/tracing/latency/Makefile | 48 ++++---
tools/tracing/latency/Makefile.config | 28 ++++
tools/tracing/rtla/.gitignore | 4 +-
tools/tracing/rtla/Build | 1 +
tools/tracing/rtla/Makefile | 177 +++++--------------------
tools/tracing/rtla/Makefile.config | 44 ++++++
tools/tracing/rtla/Makefile.rtla | 77 +++++++++++
tools/tracing/rtla/Makefile.standalone | 24 ++++
tools/tracing/rtla/src/Build | 11 ++
tools/verification/rv/.gitignore | 2 +
tools/verification/rv/Build | 1 +
tools/verification/rv/Makefile | 166 +++++------------------
tools/verification/rv/Makefile.config | 44 ++++++
tools/verification/rv/Makefile.rv | 49 +++++++
tools/verification/rv/src/Build | 4 +
17 files changed, 387 insertions(+), 295 deletions(-)
create mode 100644 tools/tracing/latency/Build
create mode 100644 tools/tracing/latency/Makefile.config
create mode 100644 tools/tracing/rtla/Build
create mode 100644 tools/tracing/rtla/Makefile.config
create mode 100644 tools/tracing/rtla/Makefile.rtla
create mode 100644 tools/tracing/rtla/Makefile.standalone
create mode 100644 tools/tracing/rtla/src/Build
create mode 100644 tools/verification/rv/.gitignore
create mode 100644 tools/verification/rv/Build
create mode 100644 tools/verification/rv/Makefile.config
create mode 100644 tools/verification/rv/Makefile.rv
create mode 100644 tools/verification/rv/src/Build
--
2.44.0
next reply other threads:[~2024-03-08 17:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 17:50 Daniel Bristot de Oliveira [this message]
2024-03-08 17:50 ` [PATCH 1/3] tools/tracing: Use tools/build makefiles on latency-collector Daniel Bristot de Oliveira
2024-03-08 17:50 ` [PATCH 2/3] tools/verification: Use tools/build makefiles on rv Daniel Bristot de Oliveira
2024-03-08 17:50 ` [PATCH 3/3] tools/rtla: Use tools/build makefiles to build rtla Daniel Bristot de Oliveira
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=cover.1709914259.git.bristot@kernel.org \
--to=bristot@kernel.org \
--cc=acme@redhat.com \
--cc=jkacur@redhat.com \
--cc=jolsa@kernel.org \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=rostedt@goodmis.org \
--cc=torvalds@linux-foundation.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).