[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#915877: marked as done (linux-perf-4.18 in Stretch bpo is not linked with libunwind)



Your message dated Sat, 29 May 2021 01:32:43 -0700 (PDT)
with message-id <60b1fc2b.1c69fb81.c249.1f99@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #915877,
regarding linux-perf-4.18 in Stretch bpo is not linked with libunwind
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
915877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915877
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
package: linux-perf-4.18
version: 4.18.6-1~bpo9+1

Package is not linked with libunwind, which makes perf report very slow when dwarf graph is used.

How to reproduce:
$ sudo perf_4.18 record -F 200 -p 38429 --call-graph dwarf sleep 120
$ time sudo perf report -G --no-inline > /dev/null

real    5m18.259s
user    5m10.644s
sys    0m7.527s

I managed to rebuild linux-perf-4.18 manually with libunwind. Using the exact same set of samples, this is how it performs:
$ time sudo perf_4.18 report -G --no-inline > /dev/null

real    0m0.846s
user    0m0.654s
sys    0m0.190s

I confirmed the followings:
 - linux-perf-4.9 is linked with libunwind and performs properly
 - linux-perf-* packages in sid/experimental are also linked with libunwind
 - linux-perf-* (>4.9) in Stretch backports are not linked with libunwind and they perform poorly

I suggest to rebuild all linux-perf packages in Stretch backports with libunwind linked.

--
Szabolcs Fazekas
Ahrefs

--- End Message ---
--- Begin Message ---
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore

--- End Message ---

Reply to: