Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Ceresoli via buildroot <buildroot@buildroot.org>
To: buildroot@buildroot.org, "Alexis Lothoré" <alexis.lothore@bootlin.com>
Cc: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
	"Olivier Benjamin" <olivier.benjamin@bootlin.com>,
	"Alexis Lothoré" <alexis.lothore@bootlin.com>
Subject: Re: [Buildroot] [PATCH v2 1/2] package/linux-tools: perf: build with libtraceevent support when it is selected
Date: Mon, 21 Jul 2025 10:19:26 +0200	[thread overview]
Message-ID: <2555886.XAFRqVoOGU@booty> (raw)
In-Reply-To: <20250709-perf_libtraceevent-v2-1-3ea54fbe6b5b@bootlin.com>

On mercoledì 9 luglio 2025 17:04:14 Ora legale dell’Europa centrale 
Alexis Lothoré wrote:
>When trying to perform a custom uprobe recording on a target with perf
>built by buildroot, the recording step fails as perf can not record
>uprobes without libtraceevent support:
>
>  $ perf probe -x linked_list insert_name index
>  Target program is compiled without optimization. Skipping prologue.
>  Probe on address 0x808 to force probing at the function entry.
>
>  Added new event:
>    probe_linked_list:insert_name (on insert_name in
>/root/gdb/linked_list with index)
>
>  perf is not linked with libtraceevent, to use the new probe you can
>use tracefs:
>
>          cd /sys/kernel/tracing/
>          echo 1 > events/probe_linked_list/insert_name/enable
>          echo 1 > tracing_on
>          cat trace_pipe
>          Before removing the probe, echo 0 >
>events/probe_linked_list/insert_name/enable $ perf record -e
>probe_linked_list:insert_name ./linked_list event syntax error:
>'probe_linked_list:insert_name'
>                       \___ unsupported tracepoint
>
>  libtraceevent is necessary for tracepoint support
>  Run 'perf list' for a list of valid events
>
>   Usage: perf record [<options>] [<command>]
>      or: perf record [<options>] -- <command> [<options>]
>
>      -e, --event <event>   event selector. use 'perf list' to list
>available events
>
>libtraceevent support for perf has been disabled with commit
>b4ab45a5c1db ("package/linux-tools: disable libtracevent detection")
>because there was no libtraceevent package in buildroot to replace the
>former libtraceevent removed from the kernel sources. Since then,
>commit 1474f1b34b17 ("package/libtraceevent: new package") has
>introduced a libtraceevent package. We can then expose again the
>possibility to build perf with libtraceevent support.
>
>Make buildroot perf makefile detect if libtraceevent package has been
>enabled, and if so, allow to build perf with libtraceevent support.
>
>Signed-off-by: Alexis Lothoré <alexis.lothore@bootlin.com>

Reviewed-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Tested-by: Luca Ceresoli <luca.ceresoli@bootlin.com>

Luca

-- 
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2025-07-21  8:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-09 15:04 [Buildroot] [PATCH v2 0/2] packages/linux-tools: perf: allow building perf with libtraceevent Alexis Lothoré via buildroot
2025-07-09 15:04 ` [Buildroot] [PATCH v2 1/2] package/linux-tools: perf: build with libtraceevent support when it is selected Alexis Lothoré via buildroot
2025-07-21  8:19   ` Luca Ceresoli via buildroot [this message]
2025-12-29 17:55   ` Julien Olivain via buildroot
2026-01-13 19:45   ` Arnout Vandecappelle via buildroot
2025-07-09 15:04 ` [Buildroot] [PATCH v2 2/2] packages/linux-tools: perf: enforce PKG_CONFIG_LIBDIR Alexis Lothoré via buildroot
2025-07-21  8:20   ` Luca Ceresoli via buildroot
2026-01-13 19:45   ` Arnout Vandecappelle via buildroot

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=2555886.XAFRqVoOGU@booty \
    --to=buildroot@buildroot.org \
    --cc=alexis.lothore@bootlin.com \
    --cc=luca.ceresoli@bootlin.com \
    --cc=olivier.benjamin@bootlin.com \
    --cc=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox