From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Michael Tretter <m.tretter@pengutronix.de>
Subject: [ptxdist] [PATCH v3 2/2] kernel/perf: Make use of libtraceevent
Date: Wed, 15 May 2024 09:22:57 +0200 [thread overview]
Message-ID: <20240515072254.12082-6-u.kleine-koenig@pengutronix.de> (raw)
In-Reply-To: <20240515072254.12082-4-u.kleine-koenig@pengutronix.de>
This makes it possible to use with tracepoints and enable the
subcommands kmem, kwork, lock, sched and timechart.
Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
---
rules/kernel.in | 1 +
rules/kernel.make | 1 -
2 files changed, 1 insertion(+), 1 deletion(-)
diff --git a/rules/kernel.in b/rules/kernel.in
index 817481577..862d52598 100644
--- a/rules/kernel.in
+++ b/rules/kernel.in
@@ -6,6 +6,7 @@ menuconfig KERNEL
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
if KERNEL
diff --git a/rules/kernel.make b/rules/kernel.make
index d82aa27fb..0fe4f1e1b 100644
--- a/rules/kernel.make
+++ b/rules/kernel.make
@@ -223,7 +223,6 @@ KERNEL_TOOL_PERF_OPTS := \
NO_LIBBIONIC=1 \
NO_LIBCRYPTO=1 \
NO_LIBDW_DWARF_UNWIND= \
- NO_LIBTRACEEVENT=1 \
NO_PERF_READ_VDSO32=1 \
NO_PERF_READ_VDSOX32=1 \
NO_ZLIB= \
--
2.39.2
next prev parent reply other threads:[~2024-05-15 7:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 7:22 [ptxdist] [PATCH v3 0/2] add libtraceevent for perf Uwe Kleine-König
2024-05-15 7:22 ` [ptxdist] [PATCH v3 1/2] libtraceevent: new package Uwe Kleine-König
2024-05-21 9:58 ` [ptxdist] [APPLIED] " Michael Olbrich
2024-05-15 7:22 ` Uwe Kleine-König [this message]
2024-05-21 9:58 ` [ptxdist] [APPLIED] kernel/perf: Make use of libtraceevent 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=20240515072254.12082-6-u.kleine-koenig@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=m.tretter@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