From: Lucas Stach <l.stach@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH] kernel/perf: enable jevents
Date: Fri, 31 May 2024 21:51:44 +0200 [thread overview]
Message-ID: <20240531195144.1849501-1-l.stach@pengutronix.de> (raw)
perf jevents are metrics that build on top of the raw perf events and
can provide much more insight at a glance than the raw numbers. Enable
them by default as the only dependency is host-python to generate the
C files to build into the perf target tool from the json description.
Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
---
rules/kernel.in | 13 +++++++------
rules/kernel.make | 1 -
2 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/rules/kernel.in b/rules/kernel.in
index 862d52598556..46c2267b6df3 100644
--- a/rules/kernel.in
+++ b/rules/kernel.in
@@ -2,12 +2,13 @@
menuconfig KERNEL
bool "kernel tools "
- select LIBELF if KERNEL_TOOL_PERF
- select LIBELF_LIBDW if KERNEL_TOOL_PERF
- select SLANG if KERNEL_TOOL_PERF
- select BINUTILS if KERNEL_TOOL_PERF
- select LIBTRACEEVENT if KERNEL_TOOL_PERF
- select LIBUNWIND if KERNEL_TOOL_PERF
+ select LIBELF if KERNEL_TOOL_PERF
+ select LIBELF_LIBDW if KERNEL_TOOL_PERF
+ select SLANG if KERNEL_TOOL_PERF
+ select BINUTILS if KERNEL_TOOL_PERF
+ select LIBTRACEEVENT if KERNEL_TOOL_PERF
+ select LIBUNWIND if KERNEL_TOOL_PERF
+ select HOST_SYSTEM_PYTHON3 if KERNEL_TOOL_PERF
if KERNEL
diff --git a/rules/kernel.make b/rules/kernel.make
index 0fe4f1e1b12a..9a61d4402ee0 100644
--- a/rules/kernel.make
+++ b/rules/kernel.make
@@ -214,7 +214,6 @@ KERNEL_TOOL_PERF_OPTS := \
NO_SLANG= \
NO_GTK2=1 \
NO_DEMANGLE= \
- NO_JEVENTS=1 \
NO_LIBELF= \
NO_LIBUNWIND=1 \
NO_BACKTRACE= \
--
2.39.2
next reply other threads:[~2024-05-31 19:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 19:51 Lucas Stach [this message]
2024-06-10 19:41 ` [ptxdist] [APPLIED] " Michael Olbrich
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=20240531195144.1849501-1-l.stach@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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