aboutsummaryrefslogtreecommitdiffstats
path: root/tools/perf/builtin-script.c
diff options
context:
space:
mode:
authorBlake Jones <[email protected]>2025-06-12 19:49:35 +0000
committerNamhyung Kim <[email protected]>2025-06-20 21:48:14 +0000
commit1d0654b7fdc5431b85035f6e76b4bc57679575d8 (patch)
tree20e52c0cbc88f33780a68a94bc454f2c55808e1c /tools/perf/builtin-script.c
parentperf header: remove unecessary core id test (diff)
downloadkernel-1d0654b7fdc5431b85035f6e76b4bc57679575d8.tar.gz
kernel-1d0654b7fdc5431b85035f6e76b4bc57679575d8.zip
perf build: detect support for libbpf's emit_strings option
This creates a config option that detects libbpf's ability to display character arrays as strings, which was just added to the BPF tree (https://git.kernel.org/bpf/bpf-next/c/87c9c79a02b4). To test this change, I built perf (from later in this patch set) with: - static libbpf (default, using source from kernel tree) - dynamic libbpf (LIBBPF_DYNAMIC=1 LIBBPF_INCLUDE=/usr/local/include) For both the static and dynamic versions, I used headers with and without the ".emit_strings" option. I verified that of the four resulting binaries, the two with ".emit_strings" would successfully record BPF_METADATA events, and the two without wouldn't. All four binaries would successfully display BPF_METADATA events, because the relevant bit of libbpf code is only used during "perf record". Signed-off-by: Blake Jones <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Namhyung Kim <[email protected]>
Diffstat (limited to 'tools/perf/builtin-script.c')
0 files changed, 0 insertions, 0 deletions