From: "Alexei Starovoitov" <alexei.starovoitov@gmail.com>
To: "Wang Yibo" <szwyb123@gmail.com>
Cc: <bpf@vger.kernel.org>, <daniel@iogearbox.net>,
<andrii@kernel.org>, <eddyz87@gmail.com>, <memxor@gmail.com>,
<yonghong.song@linux.dev>
Subject: Re: [PATCH v3 bpf-next 0/6] bpf: Unwinding with unwind_goto and unwind_exit
Date: Wed, 21 Oct 2026 16:55:18 +0000 [thread overview]
Message-ID: <DMAO9WXLPZ4Q.3KZLMI783AR3Y@gmail.com> (raw)
In-Reply-To: <20261021011249.17-1-szwyb123@gmail.com>
On Tue, Oct 20, 2026 at 06:12 PM Wang Yibo <szwyb123@gmail.com> wrote:
> I tested v3 on arm64. The cover letter says test_progs was only run on
> x86-64 and freplace was not run on arm64, so that is the part I tried to
> cover.
Thanks for testing.
unwind_exit in arm64 JIT is different v4. No autia1716 and pacia1716.
The epilogue authenticates LR as it is and adds the offset of the pad
to it.
next prev parent reply other threads:[~2026-10-21 16:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 4:33 [PATCH v3 bpf-next 0/6] bpf: Unwinding with unwind_goto and unwind_exit Alexei Starovoitov
2026-10-20 4:33 ` [PATCH v3 bpf-next 1/6] bpf: Add unwind_goto and unwind_exit insns Alexei Starovoitov
2026-10-20 8:15 ` sashiko-bot
2026-10-20 4:33 ` [PATCH v3 bpf-next 2/6] bpf, x86: Support unwind_goto and unwind_exit Alexei Starovoitov
2026-10-20 4:33 ` [PATCH v3 bpf-next 3/6] bpf, arm64: " Alexei Starovoitov
2026-10-20 4:33 ` [PATCH v3 bpf-next 4/6] selftests/bpf: Add tests for " Alexei Starovoitov
2026-10-20 5:10 ` bot+bpf-ci
2026-10-20 4:33 ` [PATCH v3 bpf-next 5/6] selftests/bpf: Add a C++ prog with exceptions Alexei Starovoitov
2026-10-20 5:10 ` bot+bpf-ci
2026-10-20 4:33 ` [PATCH v3 bpf-next 6/6] selftests/bpf: Test unwinding from R0:R2 subprog Alexei Starovoitov
2026-10-21 1:12 ` [PATCH v3 bpf-next 0/6] bpf: Unwinding with unwind_goto and unwind_exit Wang Yibo
2026-10-21 16:55 ` Alexei Starovoitov [this message]
2026-10-22 5:21 ` Wang Yibo
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=DMAO9WXLPZ4Q.3KZLMI783AR3Y@gmail.com \
--to=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=memxor@gmail.com \
--cc=szwyb123@gmail.com \
--cc=yonghong.song@linux.dev \
/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