From: Tony Jones <tonyj@suse.de>
To: Ian Rogers <irogers@google.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v1] perf addr2line: Add a libdw implementation
Date: Thu, 8 Jan 2026 14:37:24 -0800 [thread overview]
Message-ID: <aWAxpIBX4mddAdBm@suse.de> (raw)
In-Reply-To: <CAP-5=fUd95Hw8opxtCA+5aO5-6V6_Y0FMPOCCSmfwsDP6YnzeQ@mail.gmail.com>
On Thu, Jan 01, 2026 at 12:17:08PM -0800, Ian Rogers wrote:
> On Fri, Dec 12, 2025 at 8:34 AM Tony Jones <tonyj@suse.de> wrote:
> >
> > On Thu, Dec 11, 2025 at 09:20:35PM -0800, Ian Rogers wrote:
> > > Thanks Tony, those are great performance numbers! I'm wondering now:
> > > - do we want to land addr2line with libdw given the wrong file/line#
> > > problems or wait for a fix?
> > > - do we want to make the addr2line configurable like with objdump [1] to
> > > mitigate the problem above?
> >
> > I think we should spend a bit more time understanding the former before
> > doing the later. If only to provide some documentation on why there
> > is a deviance to explain the configurability.
>
> Thanks Tony, did you get a chance to look at this?
Not yet, maybe next week. It didn't feel like a time critical issue
and I had other more pressing things to look at.
--
Tony Jones
SUSE Kernel Performance Team
next prev parent reply other threads:[~2026-01-08 22:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-22 9:39 [PATCH v1] perf addr2line: Add a libdw implementation Ian Rogers
2025-11-24 11:21 ` James Clark
2025-11-26 18:27 ` Namhyung Kim
2025-11-27 11:43 ` Ian Rogers
2025-11-27 12:16 ` James Clark
2025-11-27 13:19 ` Ian Rogers
2025-11-27 13:48 ` James Clark
2025-11-28 9:00 ` Ian Rogers
2025-11-28 14:25 ` James Clark
2025-12-11 23:35 ` Tony Jones
[not found] ` <CAP-5=fUbZ1pjvcbF0do8BrC0NAzkOJeQUAozQhXKpGuosrW3ew@mail.gmail.com>
2025-12-12 16:34 ` Tony Jones
2026-01-01 20:17 ` Ian Rogers
2026-01-08 22:37 ` Tony Jones [this message]
2026-01-09 23:01 ` Ian Rogers
2025-11-27 20:53 ` Namhyung Kim
2025-11-28 8:42 ` Ian Rogers
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=aWAxpIBX4mddAdBm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox