From: sashiko-bot@kernel.org
To: "Alireza Haghdoost" <haghdoost@uber.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v7 4/4] perf test: Test lazy symbol name loading
Date: Sat, 14 Nov 2026 05:19:38 +0000 [thread overview]
Message-ID: <sashiko-outbox-214167@kernel.org> (raw)
In-Reply-To: <20261113-perf-symbol-memory-send-v7-4-d992eced9f9c@uber.com>
> From: Alireza Haghdoost <haghdoost@uber.com>
>
> Add a "Lazy symbol loading" unit test suite. It covers duplicate
> selection without names, lazy names that take one or more reads or
> cannot be read at all, lookups from several threads while another one
> walks the symbols, eager and lazy parity on a real DSO (perf itself, or
> the one given with --dso), and a symbol table file that is replaced
> after the first name was read.
>
> Add two shell tests. lazy_load_symbols_parity.sh runs the parity test
> on four small binaries built for the loader's corner cases: split
> debuginfo whose function section is NOBITS in the debug file, a shared
> library with .dynsym-only symbols and aliases, a stripped library with
> .gnu_debugdata, and on x86_64 an IFUNC behind an IRELATIVE PLT slot.
> script_lazy_load_symbols.sh records a small callchain profile and checks
> that perf script prints the same output with and without
> --lazy-load-symbols. As root, it also checks that names are read from
> the build-id cache when the profiled process is in another mount
> namespace.
>
> Both shell tests skip a case, rather than fail it, when the toolchain
> produced a file whose names perf loads eagerly anyway (PPC64 ELFv1 .opd,
> .gnu_debugdata or a compressed .strtab).
>
> Signed-off-by: Alireza Haghdoost <haghdoost@uber.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261113-perf-symbol-memory-send-v7-0-d992eced9f9c@uber.com?part=4
prev parent reply other threads:[~2026-11-14 5:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-14 5:09 [PATCH v7 0/4] perf script: Lazy symbol loading Alireza Haghdoost
2026-11-14 5:09 ` Alireza Haghdoost via B4 Relay
2026-11-14 5:09 ` [PATCH v7 1/4] perf symbols: Split out name-independent duplicate symbol selection Alireza Haghdoost
2026-11-14 5:09 ` Alireza Haghdoost via B4 Relay
2026-11-14 5:12 ` sashiko-bot
2026-11-14 5:09 ` [PATCH v7 2/4] perf symbols: Point to the symbol name instead of embedding it Alireza Haghdoost
2026-11-14 5:09 ` Alireza Haghdoost via B4 Relay
2026-11-14 5:16 ` sashiko-bot
2026-11-14 5:09 ` [PATCH v7 3/4] perf script: Add --lazy-load-symbols to load symbol names lazily Alireza Haghdoost
2026-11-14 5:09 ` Alireza Haghdoost via B4 Relay
2026-11-14 5:31 ` sashiko-bot
2026-11-14 5:09 ` [PATCH v7 4/4] perf test: Test lazy symbol name loading Alireza Haghdoost
2026-11-14 5:09 ` Alireza Haghdoost via B4 Relay
2026-11-14 5:19 ` sashiko-bot [this message]
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=sashiko-outbox-214167@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=haghdoost@uber.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.