From: Tony Jones <tonyj@suse.de>
To: Ian Rogers <irogers@google.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: addr2line performance
Date: Fri, 31 Oct 2025 10:01:27 -0700 [thread overview]
Message-ID: <aQTrZ54mkx14r_cQ@suse.de> (raw)
In-Reply-To: <CAP-5=fU4y2y+pOT590GZG-A+zO5YdAAzUyPgUX5RTji0nh6Z+g@mail.gmail.com>
On Wed, Oct 29, 2025 at 08:51:12AM -0700, Ian Rogers wrote:
>
> I'm not sure there is an explicit discussion rather than discussion on
> individual patch sets.
Thanks for the reply. I thought the original comment in that BZ
was talking about plans to remove the current forking of an "addr2line"
process and communicating via pipe with some library implementation.
Of course what that library would be if not BFD/LLVM was my question.
Clearly this was a misread on my part.
I'd seen the patches related to dlopen'ing llvm, backporting this is
a possibility since we don't want a rpm requires.
Cheers!
Tony
--
Tony Jones
SUSE Kernel Performance Team
next prev parent reply other threads:[~2025-10-31 17:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 18:30 addr2line performance Tony Jones
2025-10-29 15:51 ` Ian Rogers
2025-10-31 17:01 ` Tony Jones [this message]
2025-10-31 17:49 ` Ian Rogers
2025-10-31 19:39 ` Namhyung Kim
2025-10-31 20:40 ` Tony Jones
2025-11-04 3:16 ` Namhyung Kim
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=aQTrZ54mkx14r_cQ@suse.de \
--to=tonyj@suse.de \
--cc=irogers@google.com \
--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 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.