From: James Clark <james.clark@arm.com>
To: Ian Rogers <irogers@google.com>
Cc: linux-perf-users <linux-perf-users@vger.kernel.org>,
ChaitanyaS.Prakash@arm.com
Subject: Re: Issues with Linux perf tool on Raspberry Pi 5
Date: Tue, 23 Jan 2024 16:40:12 +0000 [thread overview]
Message-ID: <c395aa13-c658-a807-bcb4-a6b31401ef4f@arm.com> (raw)
In-Reply-To: <CAP-5=fXuduT--u5WThgi5RO1d8G5DuAUfn_AVjWTr6=VtZAUWQ@mail.gmail.com>
On 22/01/2024 22:39, Ian Rogers wrote:
> On Mon, Jan 22, 2024 at 1:59 AM James Clark <james.clark@arm.com> wrote:
>>
>> On 19/01/2024 23:39, Ian Rogers wrote:
>>> Hi,
>>>
>>> I thought I'd report the state of Linux perf tests on Raspberry Pi 5
>>> and so I opened a bug because of the number of failures. I'm happy for
>>> help resolving the issues. The bug is:
>>> https://bugzilla.kernel.org/show_bug.cgi?id=218401
>>>
>>> Thanks,
>>> Ian
>>>
>>
>> Hi Ian,
>>
>> For "test perf probe of function from different CU", Chaitanya has a fix
>> that she should be sending soon. I already planned to look at "Check
>> Arm64 callgraphs are complete in fp mode" as I see that failing here so
>> it's not related to Rpi5.
>>
I see that "test dwarf unwind" is completely missing in your output, not
even skipped. This suggests that libdwarf isn't linked in:
#ifdef HAVE_DWARF_UNWIND_SUPPORT
&suite__dwarf_unwind,
#endif
"Check Arm64 callgraphs are complete in fp mode" relies on a Dwarf
unwinder so I sent a patch to skip this test if one isn't linked in.
prev parent reply other threads:[~2024-01-23 16:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 23:39 Issues with Linux perf tool on Raspberry Pi 5 Ian Rogers
2024-01-20 0:55 ` Namhyung Kim
2024-01-20 4:27 ` Ian Rogers
2024-01-20 6:31 ` Ian Rogers
2024-01-22 9:59 ` James Clark
2024-01-22 22:39 ` Ian Rogers
2024-01-23 16:40 ` James Clark [this message]
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=c395aa13-c658-a807-bcb4-a6b31401ef4f@arm.com \
--to=james.clark@arm.com \
--cc=ChaitanyaS.Prakash@arm.com \
--cc=irogers@google.com \
--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 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).