From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: James Clark <james.clark@linaro.org>
Cc: Christophe Leroy <christophe.leroy@csgroup.eu>,
"linux-perf-users@vger.kernel.org"
<linux-perf-users@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Namhyung Kim <namhyung@kernel.org>
Subject: Re: Perf doesn't display kernel symbols anymore (bisected commit 659ad3492b91 ("perf maps: Switch from rbtree to lazily sorted array for addresses"))
Date: Thu, 26 Dec 2024 12:51:20 -0300 [thread overview]
Message-ID: <Z217eBsXIaSgKuSs@x1> (raw)
In-Reply-To: <53f3abe5-dd22-4a1a-82e6-bc88e91d1869@linaro.org>
On Tue, Dec 17, 2024 at 02:18:07PM +0000, James Clark wrote:
> On 16/12/2024 7:01 am, Christophe Leroy wrote:
> > I noticed with 6.12 LTS Kernel that perf top and perf record/report
> > don't display kernel symbols anymore, instead it displays the raw
> > address with [unknown] as object.
> > After bisect I see that the problem appears with commit 659ad3492b91
> > ("perf maps: Switch from rbtree to lazily sorted array for addresses").
> You might want to try applying 0b90dfda222e3 as it claims to fix this
> commit. I doubt that will fix your issue but it's worth being sure.
> There was also another fix recently that could be related: 23c44f6c83
> Did you try the perf-tools-next branch? Maybe something that's already fixed
> needs to be backported.
Right, I tried reproducing this on perf-tools-next and couldn't, so
please test it there.
Thanks,
- Arnaldo
next prev parent reply other threads:[~2024-12-26 15:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 7:01 Perf doesn't display kernel symbols anymore (bisected commit 659ad3492b91 ("perf maps: Switch from rbtree to lazily sorted array for addresses")) Christophe Leroy
2024-12-17 14:18 ` James Clark
2024-12-17 14:50 ` Christophe Leroy
2024-12-26 15:51 ` Arnaldo Carvalho de Melo [this message]
2025-01-02 14:41 ` Christophe Leroy
2025-01-02 17:52 ` Christophe Leroy
2025-01-02 18:19 ` Arnaldo Carvalho de Melo
2025-01-02 19:42 ` Christophe Leroy
2025-01-03 1:08 ` Arnaldo Carvalho de Melo
2025-01-03 6:33 ` Christophe Leroy
2025-01-03 12:40 ` Christophe Leroy
2025-01-03 16:26 ` Arnaldo Carvalho de Melo
2025-01-06 12:38 ` Christophe Leroy
2025-01-06 21:46 ` Namhyung Kim
2025-01-08 17:55 ` Christophe Leroy
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=Z217eBsXIaSgKuSs@x1 \
--to=acme@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=james.clark@linaro.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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).