From: "Steinar H. Gunderson" <sesse@google.com>
To: acme@kernel.org
Cc: linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
irogers@google.com
Subject: Re: [PATCH v2] Add a trie to map quickly from address range to compilation unit.
Date: Sat, 18 May 2024 18:54:26 +0200 [thread overview]
Message-ID: <ZkjdQqN1dPsZDDRA@google.com> (raw)
In-Reply-To: <20240518165315.3963142-1-sesse@google.com>
On Sat, May 18, 2024 at 06:53:11PM +0200, Steinar H. Gunderson wrote:
> When using perf to profile large binaries, _bfd_dwarf2_find_nearest_line()
> becomes a hotspot, as perf wants to get line number information
> (for inline-detection purposes) for each and every sample. In Chromium
> in particular (the content_shell binary), this entails going through
> 475k address ranges, which takes a long time when done repeatedly.
I accidentally sent out an ancient patch anew; sorry, please ignore.
/* Steinar */
next prev parent reply other threads:[~2024-05-18 16:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-18 16:53 [PATCH v2] Add a trie to map quickly from address range to compilation unit Steinar H. Gunderson
2024-05-18 16:54 ` Steinar H. Gunderson [this message]
2024-05-19 15:50 ` Ian Rogers
2024-05-19 20:58 ` Steinar H. Gunderson
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=ZkjdQqN1dPsZDDRA@google.com \
--to=sesse@google.com \
--cc=acme@kernel.org \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).