Linux Perf Users
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Matthew Wood" <thepacketgeek@gmail.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v2 3/3] perf unwind: Don't look up symbols when the caller doesn't want them
Date: Sat, 17 Oct 2026 00:15:43 +0000	[thread overview]
Message-ID: <sashiko-outbox-175061@kernel.org> (raw)
In-Reply-To: <20261017000158.1178269-4-thepacketgeek@gmail.com>

> Commit 02b2705017d2 ("perf callchain: Allow symbols to be optional when
> resolving a callchain") let callers that only need maps, such as
> build-id marking in 'perf record' and 'perf inject', resolve callchains
> without loading symbols. The DWARF unwinders were left out:
> thread__resolve_callchain_unwind() just notes that "Not resolving
> symbols with an unwinder isn't currently supported", and both libdw and
> libunwind look up the symbol of every frame they visit. The first lookup
> in a DSO loads its whole symbol table and demangles every name in it.
> 
> On arm64 this happens even for frame pointer callchains, because
> get_leaf_frame_caller_aarch64() runs a two frame DWARF unwind for every
> sample to recover the leaf function's caller. Since commit 29be60c93d2d
> ("perf build-id: Mark DSO in sample callchains"), process_buildids()
> does that for every sample at the end of 'perf record', so with -a it
> loads and demangles the symbol tables of every user binary sampled on
> [ ... ]
> and 15.5MB, with the same build-ids injected.
> 
> Fixes: 02b2705017d2 ("perf callchain: Allow symbols to be optional when resolving a callchain")
> Fixes: 29be60c93d2d ("perf build-id: Mark DSO in sample callchains")
> Signed-off-by: Matthew Wood <thepacketgeek@gmail.com>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261017000158.1178269-1-thepacketgeek@gmail.com?part=3


      reply	other threads:[~2026-10-17  0:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-17  0:01 [PATCH v2 0/3] perf unwind: Don't load symbols when the caller doesn't need them Matthew Wood
2026-10-17  0:01 ` [PATCH v2 1/3] perf dso: Move dso__read_build_id() from perf inject to dso.c Matthew Wood
2026-10-17  0:05   ` sashiko-bot
2026-10-17  0:01 ` [PATCH v2 2/3] perf unwind: Find separate debuginfo without loading symbols Matthew Wood
2026-10-17  0:18   ` sashiko-bot
2026-10-17  0:01 ` [PATCH v2 3/3] perf unwind: Don't look up symbols when the caller doesn't want them Matthew Wood
2026-10-17  0:15   ` 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-175061@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=thepacketgeek@gmail.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