[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <173082489932.149345.16688202672767622276.b4-ty@kernel.org>
Date: Tue, 05 Nov 2024 08:41:39 -0800
From: Namhyung Kim <namhyung@...nel.org>
To: Peter Zijlstra <peterz@...radead.org>, Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...nel.org>, Adrian Hunter <adrian.hunter@...el.com>,
Kan Liang <kan.liang@...ux.intel.com>, linux-perf-users@...r.kernel.org,
linux-kernel@...r.kernel.org, Ian Rogers <irogers@...gle.com>
Subject: Re: [PATCH v2] perf build: Make libunwind opt-in rather than
opt-out
On Mon, 28 Oct 2024 12:36:19 -0700, Ian Rogers wrote:
> Having multiple unwinding libraries makes the perf code harder to
> understand and we have unused/untested code paths.
>
> Perf made BPF support an opt-out rather than opt-in feature. As libbpf
> has a libelf dependency, elfutils that provides libelf will also
> provide libdw. When libdw is present perf will use libdw unwinding
> rather than libunwind unwinding even if libunwind support is compiled
> in.
>
> [...]
Applied to perf-tools-next, thanks!
Best regards,
Namhyung
Powered by blists - more mailing lists