From: James Clark <james.clark@arm.com>
To: John Garry <john.garry@huawei.com>, alexandre.truong@arm.com
Cc: linux-perf-users@vger.kernel.org,
"jolsa@kernel.org >> Jiri Olsa" <jolsa@kernel.org>,
german.gomez@arm.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>
Subject: Re: perf tool: About "perf arm64: Inject missing frames when using 'perf record --call-graph=fp'"
Date: Wed, 6 Apr 2022 10:08:42 +0100 [thread overview]
Message-ID: <2dc4266f-02b1-0937-a884-dfa037cc7ffd@arm.com> (raw)
In-Reply-To: <5f1d8b3f-0afa-2724-4ff1-f061939c68c5@huawei.com>
On 05/04/2022 15:04, John Garry wrote:
> Hi Alexandre,
>
> I notice that with commit b9f6fbb3b2c2 ("perf arm64: Inject missing frames when using 'perf record --call-graph=fp'") that I get messages spewing the console when running perf record+report, as below:
>
> john@ubuntu:~/linux$sudo tools/perf/perf record -ag fio null12.fio
> john@ubuntu:~/linux$sudo tools/perf/perf report > report
> unwind: can't read reg 29
> unwind: can't read reg 29
> unwind: can't read reg 29
> unwind: can't read reg 29
> ...
>
> Do you know the possible cause? I haven't checked...
Hi John,
I'm going to look into this today. I expect the cause is because we only record
the link register for this change and then do a best effort unwind to see if
we can get the return address just from that. So I don't think this is a major issue,
probably the outcome will be that I mask any of these errors just for this call
to libunwind that we added. The other main call to libunwind should still print
these errors.
One thing that is interesting is why we didn't see this when we were testing
the patch before, and we've also found it a little bit difficult to reproduce here.
So there might be more to it than just masking the error, but I'm not sure yet.
Either way, I don't expect that any unwinding is broken, just that it's
printing an annoying message.
James
>
> Thanks,
> john
next prev parent reply other threads:[~2022-04-06 13:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 14:04 perf tool: About "perf arm64: Inject missing frames when using 'perf record --call-graph=fp'" John Garry
2022-04-06 9:08 ` James Clark [this message]
2022-04-06 11:28 ` John Garry
2022-04-06 15:00 ` James Clark
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=2dc4266f-02b1-0937-a884-dfa037cc7ffd@arm.com \
--to=james.clark@arm.com \
--cc=acme@kernel.org \
--cc=alexandre.truong@arm.com \
--cc=german.gomez@arm.com \
--cc=john.garry@huawei.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.