From: Yonghong Song <yonghong.song@linux.dev>
To: Amery Hung <ameryhung@gmail.com>
Cc: bpf@vger.kernel.org, Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
"Jose E . Marchesi" <jose.marchesi@oracle.com>,
kernel-team@fb.com, Martin KaFai Lau <martin.lau@kernel.org>
Subject: Re: [PATCH bpf-next 07/10] bpf,x86: Implement JIT support for stack arguments
Date: Thu, 2 Apr 2026 16:26:27 -0700 [thread overview]
Message-ID: <72a624c9-28c2-44df-a61f-30b37366304a@linux.dev> (raw)
In-Reply-To: <CAMB2axMGn8wWTWDiDQUTAS5A2Ey0FGMxEu-FryvaLAv_UBhrTA@mail.gmail.com>
On 4/2/26 3:26 PM, Amery Hung wrote:
> On Wed, Apr 1, 2026 at 6:28 PM Yonghong Song <yonghong.song@linux.dev> wrote:
> [...]
>
>> case BPF_JMP | BPF_CALL: {
>> + int off, base_off, n_stack_args, kfunc_stack_args = 0, stack_args = 0;
>> + u16 outgoing_stack_args = stack_arg_depth - incoming_stack_arg_depth;
>> u8 *ip = image + addrs[i - 1];
>>
>> func = (u8 *) __bpf_call_base + imm32;
>> @@ -2449,6 +2549,29 @@ st: if (is_imm8(insn->off))
>> }
>> if (!imm32)
>> return -EINVAL;
>> +
>> + if (src_reg == BPF_PSEUDO_CALL && outgoing_stack_args > 0) {
>> + n_stack_args = outgoing_stack_args / 8;
>> + base_off = -(prog_stack_depth + incoming_stack_arg_depth);
>> + ip += push_stack_args(&prog, base_off, n_stack_args, 1);
>> + }
>> +
>> + if (src_reg != BPF_PSEUDO_CALL && insn->off > 0) {
>> + kfunc_stack_args = insn->off;
>> + stack_args = kfunc_stack_args > 1 ? kfunc_stack_args - 1 : 0;
>> + base_off = -(prog_stack_depth + incoming_stack_arg_depth);
>> + ip += push_stack_args(&prog, base_off, kfunc_stack_args, 2);
>> +
>> + /* mov r9, [rbp + base_off - 8] */
>> + off = base_off - 8;
>> + if (is_imm8(off)) {
>> + EMIT4(0x4C, 0x8B, 0x4D, off);
>> + ip += 4;
>> + } else {
>> + EMIT3_off32(0x4C, 0x8B, 0x8D, off);
>> + ip += 7;
>> + }
>> + }
> Do we need to make sure RSP is 16-byte aligned before passing arg
> through stack per x86-64 ABI?
Good question. Without this patch set, looks like bpf jit here does not enforce 16 byte
aligned. IIUC, 16 byte aligned requirement will be necessary for some special
SSE/AVX/128-bit XMM etc. The bpf jit does not really emit them, so I guess it is okay?
>
>> if (priv_frame_ptr) {
>> push_r9(&prog);
>> ip += 2;
>> @@ -2458,6 +2581,14 @@ st: if (is_imm8(insn->off))
>> return -EINVAL;
>> if (priv_frame_ptr)
>> pop_r9(&prog);
>> + if (stack_args > 0) {
>> + /* add rsp, stack_args * 8 */
>> + EMIT4(0x48, 0x83, 0xC4, stack_args * 8);
>> + }
>> + if (src_reg == BPF_PSEUDO_CALL && outgoing_stack_args > 0) {
>> + /* add rsp, outgoing_stack_args */
>> + EMIT4(0x48, 0x83, 0xC4, outgoing_stack_args);
>> + }
>> break;
>> }
>>
>> --
>> 2.52.0
>>
>>
next prev parent reply other threads:[~2026-04-02 23:27 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 1:27 [PATCH bpf-next 00/10] bpf: Support stack arguments for BPF functions and kfuncs Yonghong Song
2026-04-02 1:27 ` [PATCH bpf-next 01/10] bpf: Introduce bpf register BPF_REG_STACK_ARG_BASE Yonghong Song
2026-04-02 1:27 ` [PATCH bpf-next 02/10] bpf: Reuse MAX_BPF_FUNC_ARGS for maximum number of arguments Yonghong Song
2026-04-02 1:27 ` [PATCH bpf-next 03/10] bpf: Support stack arguments for bpf functions Yonghong Song
2026-04-02 3:18 ` bot+bpf-ci
2026-04-02 14:42 ` Yonghong Song
2026-04-02 18:55 ` Amery Hung
2026-04-02 20:45 ` Yonghong Song
2026-04-02 23:38 ` Amery Hung
2026-04-03 4:05 ` Yonghong Song
2026-04-02 23:38 ` Alexei Starovoitov
2026-04-03 4:10 ` Yonghong Song
2026-04-05 21:07 ` Alexei Starovoitov
2026-04-06 4:29 ` Yonghong Song
2026-04-06 4:51 ` Alexei Starovoitov
2026-04-06 6:03 ` Yonghong Song
2026-04-06 15:17 ` Alexei Starovoitov
2026-04-06 16:19 ` Yonghong Song
2026-04-06 17:24 ` Alexei Starovoitov
2026-04-02 1:27 ` [PATCH bpf-next 04/10] bpf: Support stack arguments for kfunc calls Yonghong Song
2026-04-02 3:18 ` bot+bpf-ci
2026-04-02 14:45 ` Yonghong Song
2026-04-02 21:02 ` Amery Hung
2026-04-02 1:27 ` [PATCH bpf-next 05/10] bpf: Reject stack arguments in non-JITed programs Yonghong Song
2026-04-02 1:27 ` [PATCH bpf-next 06/10] bpf: Enable stack argument support for x86_64 Yonghong Song
2026-04-02 1:28 ` [PATCH bpf-next 07/10] bpf,x86: Implement JIT support for stack arguments Yonghong Song
2026-04-02 22:26 ` Amery Hung
2026-04-02 23:26 ` Yonghong Song [this message]
2026-04-02 23:51 ` Alexei Starovoitov
2026-04-03 4:13 ` Yonghong Song
2026-04-02 1:28 ` [PATCH bpf-next 08/10] selftests/bpf: Add tests for BPF function " Yonghong Song
2026-04-02 1:28 ` [PATCH bpf-next 09/10] selftests/bpf: Add negative test for oversized kfunc stack argument Yonghong Song
2026-04-02 1:28 ` [PATCH bpf-next 10/10] selftests/bpf: Add verifier tests for stack argument validation Yonghong Song
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=72a624c9-28c2-44df-a61f-30b37366304a@linux.dev \
--to=yonghong.song@linux.dev \
--cc=ameryhung@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jose.marchesi@oracle.com \
--cc=kernel-team@fb.com \
--cc=martin.lau@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