From: Leo Yan <leo.yan@arm.com>
To: Puranjay Mohan <puranjay12@gmail.com>
Cc: Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Rob Herring <robh+dt@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Martin KaFai Lau <martin.lau@kernel.org>,
Eduard Zingerman <eddyz87@gmail.com>,
Kumar Kartikeya Dwivedi <memxor@gmail.com>,
Breno Leitao <leitao@debian.org>,
linux-arm-kernel@lists.infradead.org,
linux-perf-users@vger.kernel.org, kernel-team@meta.com
Subject: Re: [RFC PATCH] perf/arm64: Add BRBE support for bpf_get_branch_snapshot()
Date: Mon, 5 Jan 2026 21:22:13 +0000 [thread overview]
Message-ID: <20260105212213.GA336318@e132581.arm.com> (raw)
In-Reply-To: <CANk7y0j7hAJ7OcH_HgN0cVGnUh=iBz=iuD9sYZmSy-koMjB_cg@mail.gmail.com>
Hi,
On Fri, Jan 02, 2026 at 09:51:15PM +0000, Puranjay Mohan wrote:
> Hi Catalin, Will, Mark, and Rob.
>
> I don't have access to BRBE enabled hardware and Qemu doesn't support
> this as well therefore I just sent the compile tested version.
>
> Can you help me with testing this:
>
> The relevant bpf self test is:
>
> ./test_progs -t get_branch_snapshot
> #132 get_branch_snapshot:SKIP
> Summary: 1/0 PASSED, 1 SKIPPED, 0 FAILED
>
> skipped for my setup as it is not supported.
eBPF selftest build is quite heavy (many dependencies), finally I built
it cleanly.
I did a test on FVP RevC, the test hit NULL pointer deference and kernel
panic in armv8pmu_sched_task(). See https://termbin.com/peg4, the
backtrace should can give you hints for the issue.
Thanks,
Leo
P.s. some logs are duplicate, this might be caused by two cores both hit
the NULL pointer issue ?
next prev parent reply other threads:[~2026-01-05 21:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-02 21:40 [RFC PATCH] perf/arm64: Add BRBE support for bpf_get_branch_snapshot() Puranjay Mohan
2026-01-02 21:51 ` Puranjay Mohan
2026-01-05 21:22 ` Leo Yan [this message]
2026-01-05 21:46 ` Puranjay Mohan
2026-01-06 10:54 ` Leo Yan
2026-01-05 17:49 ` Mark Rutland
2026-01-05 19:31 ` Puranjay Mohan
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=20260105212213.GA336318@e132581.arm.com \
--to=leo.yan@arm.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=kernel-team@meta.com \
--cc=leitao@debian.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=martin.lau@kernel.org \
--cc=memxor@gmail.com \
--cc=puranjay12@gmail.com \
--cc=robh+dt@kernel.org \
--cc=will@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