From: Frederic Weisbecker <frederic@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Ian Rogers <irogers@google.com>,
linux-perf-users <linux-perf-users@vger.kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>
Subject: Re: Can perf drop libunwind support
Date: Mon, 28 Oct 2024 18:01:18 +0100 [thread overview]
Message-ID: <Zx_DXt3ESi394mcx@localhost.localdomain> (raw)
In-Reply-To: <Zx-1tx0eH19iBpjy@x1>
Le Mon, Oct 28, 2024 at 01:03:03PM -0300, Arnaldo Carvalho de Melo a écrit :
> On Wed, Oct 23, 2024 at 02:57:05PM -0700, Ian Rogers wrote:
> > Hi,
> >
> > perf wants to build with BPF support these days. libbpf has a
> > dependency on libelf, part of elfutils. libdw is also part of elfutils
> > and amongst other things provides unwinding support. My understanding
> > is libdw unwinding is used by perf in preference to libunwind when
> > present. My suspicion is that libunwind is being feature tested,
> > linked against but then seldom or never used. Given this could perf
> > drop libunwind support in order to simplify the code base?
>
> Probably Jiri remembers the reasons for us to have support for both,
> IIRC libunwind was a bit more mature at the time and so we decided to
> have both and when some broken behaviour appears we try the other one,
> in the process trying to fix the one wioth a problem?
>
> Adding Frederic as well, this is when we started to use libunwind:
Ouch, memories are blurry... It's possible that libdw deprecated
libunwind at some point. I'm sorry I completely lost track of these
things since then :-s
thanks.
next prev parent reply other threads:[~2024-10-28 17:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 21:57 Can perf drop libunwind support Ian Rogers
2024-10-28 3:13 ` Masami Hiramatsu
2024-10-28 16:03 ` Arnaldo Carvalho de Melo
2024-10-28 17:01 ` Frederic Weisbecker [this message]
2024-10-28 19:10 ` Ian Rogers
2024-10-29 23:50 ` 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=Zx_DXt3ESi394mcx@localhost.localdomain \
--to=frederic@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=namhyung@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).