From: Hari Bathini <hbathini@linux.ibm.com>
To: adubey@linux.ibm.com, bpf@vger.kernel.org
Cc: linuxppc-dev@lists.ozlabs.org, maddy@linux.ibm.com,
ast@kernel.org, andrii@kernel.org, daniel@iogearbox.net,
shuah@kernel.org, linux-kselftest@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v7 6/7] selftest/bpf: Add tailcall verifier selftest for powerpc64
Date: Sat, 13 Jun 2026 18:12:50 +0530 [thread overview]
Message-ID: <f4248818-67dc-4044-9738-5b5bec56bd2d@linux.ibm.com> (raw)
In-Reply-To: <20260611153826.31187-7-adubey@linux.ibm.com>
On 11/06/26 9:08 pm, adubey@linux.ibm.com wrote:
> From: Abhishek Dubey <adubey@linux.ibm.com>
>
> Verifier testcase result for tailcalls:
>
> # ./test_progs -t verifier_tailcall
> #618/1 verifier_tailcall/invalid map type for tail call:OK
> #618/2 verifier_tailcall/invalid map type for tail call @unpriv:OK
> #618 verifier_tailcall:OK
> #619/1 verifier_tailcall_jit/main:OK
> #619 verifier_tailcall_jit:OK
> Summary: 2/3 PASSED, 0 SKIPPED, 0 FAILED
You may want to put a space or two before each line of the above
output to differentiate it as a command output.
>
> Signed-off-by: Abhishek Dubey <adubey@linux.ibm.com>
> ---
> .../bpf/progs/verifier_tailcall_jit.c | 69 +++++++++++++++++++
> 1 file changed, 69 insertions(+)
>
> diff --git a/tools/testing/selftests/bpf/progs/verifier_tailcall_jit.c b/tools/testing/selftests/bpf/progs/verifier_tailcall_jit.c
> index 48fa34d2959f..09d7e92c8491 100644
> --- a/tools/testing/selftests/bpf/progs/verifier_tailcall_jit.c
> +++ b/tools/testing/selftests/bpf/progs/verifier_tailcall_jit.c
> @@ -91,6 +91,75 @@ __jited(" popq %rax")
> __jited(" jmp {{.*}}") /* jump to tail call tgt */
> __jited("L0: leave")
> __jited(" {{(retq|jmp 0x)}}") /* return or jump to rethunk */
> +__arch_powerpc64
> +/* program entry for main(), regular function prologue */
> +__jited(" nop")
> +__jited("...") /* ld 2, 16(13) absent with CONFIG_PPC_KERNEL_PCREL */
> +__jited(" li 9, 0")
> +__jited(" std 9, -8(1)")
> +__jited(" mflr 0")
> +__jited(" std 0, 16(1)")
> +__jited(" stdu 1, {{.*}}(1)")
> +/* load address and call sub() via count register */
> +__jited(" lis 12, {{.*}}")
> +__jited(" sldi 12, 12, 32")
> +__jited(" oris 12, 12, {{.*}}")
> +__jited(" ori 12, 12, {{.*}}")
> +__jited(" mtctr 12")
> +__jited(" bctrl")
> +__jited(" mr 8, 3")
> +__jited(" li 8, 0")
> +__jited(" addi 1, 1, {{.*}}")
> +__jited(" ld 0, 16(1)")
> +__jited(" mtlr 0")
> +__jited(" mr 3, 8")
> +__jited(" blr")
> +__jited("...")
> +__jited("func #1")
> +/* subprogram entry for sub() */
> +__jited(" nop")
> +__jited("...") /* ld 2, 16(13) absent with CONFIG_PPC_KERNEL_PCREL */
> +/* tail call prologue for subprogram */
> +__jited(" ld 10, 0(1)")
> +__jited(" ld 9, -8(10)")
> +__jited(" cmpldi 9, 33")
> +__jited(" bt {{.*}}, {{.*}}")
> +__jited(" addi 9, 10, -8")
> +__jited(" std 9, -8(1)")
> +__jited(" lis {{.*}}, {{.*}}")
> +__jited(" sldi {{.*}}, {{.*}}, 32")
> +__jited(" oris {{.*}}, {{.*}}, {{.*}}")
> +__jited(" ori {{.*}}, {{.*}}, {{.*}}")
> +__jited(" li {{.*}}, 0")
> +__jited(" lwz 9, {{.*}}({{.*}})")
> +__jited(" slwi {{.*}}, {{.*}}, 0")
> +__jited(" cmplw {{.*}}, 9")
> +__jited(" bf 0, {{.*}}")
> +/* bpf_tail_call implementation */
> +__jited(" ld 9, -8(1)")
> +__jited(" cmpldi 9, 33")
> +__jited(" bf {{.*}}, {{.*}}")
> +__jited(" ld 9, 0(9)")
> +__jited(" cmpldi 9, 33")
> +__jited(" bt {{.*}}, {{.*}}")
> +__jited(" addi 9, 9, 1")
> +__jited(" mulli 10, {{.*}}, 8")
> +__jited(" add 10, 10, {{.*}}")
> +__jited(" ld 10, {{.*}}(10)")
> +__jited(" cmpldi 10, 0")
> +__jited(" bt {{.*}}, {{.*}}")
> +__jited(" ld 10, {{.*}}(10)")
> +__jited(" addi 10, 10, {{.*}}") /* offset depends on CONFIG_PPC_KERNEL_PCREL */
> +__jited(" mtctr 10")
> +__jited(" ld 10, -8(1)")
> +__jited(" cmpldi 10, 33")
> +__jited(" bt {{.*}}, {{.*}}")
> +__jited(" addi 10, 1, -8")
> +__jited(" std 9, 0(10)")
> +__jited(" bctr")
> +__jited(" mr 3, 8")
> +__jited(" blr")
> +
> SEC("tc")
> __naked int main(void)
> {
- Hari
next prev parent reply other threads:[~2026-06-13 12:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-11 15:38 [PATCH v7 0/7] powerpc/bpf: Add support for verifier selftest adubey
2026-06-11 15:38 ` [PATCH v7 1/7] powerpc/bpf: fix alignment of long branch trampoline address adubey
2026-06-13 12:34 ` Hari Bathini
2026-06-11 15:38 ` [PATCH v7 2/7] powerpc/bpf: Move out dummy_tramp_addr after Long branch stub adubey
2026-06-11 12:18 ` bot+bpf-ci
2026-06-13 12:37 ` Hari Bathini
2026-06-11 15:38 ` [PATCH v7 3/7] selftest/bpf: Fixing powerpc JIT disassembly failure adubey
2026-06-13 12:40 ` Hari Bathini
2026-06-11 15:38 ` [PATCH v7 4/7] selftest/bpf: Enable verifier selftest for powerpc64 adubey
2026-06-13 12:48 ` Hari Bathini
2026-06-11 15:38 ` [PATCH v7 5/7] powerpc64/bpf: fix compare instruction emitted for tailcall adubey
2026-06-13 12:41 ` Hari Bathini
2026-06-11 15:38 ` [PATCH v7 6/7] selftest/bpf: Add tailcall verifier selftest for powerpc64 adubey
2026-06-13 12:42 ` Hari Bathini [this message]
2026-06-11 15:38 ` [PATCH v7 7/7] powerpc/bpf: fix buffer overflow in JIT for large BPF programs adubey
2026-06-13 12:44 ` Hari Bathini
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=f4248818-67dc-4044-9738-5b5bec56bd2d@linux.ibm.com \
--to=hbathini@linux.ibm.com \
--cc=adubey@linux.ibm.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-kselftest@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=shuah@kernel.org \
--cc=stable@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