From: Yonghong Song <yonghong.song@linux.dev>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: bpf <bpf@vger.kernel.org>, Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Kernel Team <kernel-team@fb.com>,
Martin KaFai Lau <martin.lau@kernel.org>,
Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH bpf-next v4 09/10] bpf, x86: Jit support for nested bpf_prog_call
Date: Thu, 10 Oct 2024 21:20:53 -0700 [thread overview]
Message-ID: <64da4fb8-7e13-41fc-891e-c0f79bf778d1@linux.dev> (raw)
In-Reply-To: <CAADnVQJmEkQvAhPs3q1oYGpdO48n2JE3MnMxXgYCMoUup=UOBg@mail.gmail.com>
On 10/10/24 1:53 PM, Alexei Starovoitov wrote:
> On Thu, Oct 10, 2024 at 10:59 AM Yonghong Song <yonghong.song@linux.dev> wrote:
>> static void emit_priv_frame_ptr(u8 **pprog, struct bpf_prog *bpf_prog,
>> - enum bpf_priv_stack_mode priv_stack_mode)
>> + enum bpf_priv_stack_mode priv_stack_mode,
>> + bool is_subprog, u8 *image, u8 *temp)
>> {
>> u32 orig_stack_depth = round_up(bpf_prog->aux->stack_depth, 8);
>> u8 *prog = *pprog;
>>
>> - if (priv_stack_mode == PRIV_STACK_ROOT_PROG)
>> - emit_root_priv_frame_ptr(&prog, bpf_prog, orig_stack_depth);
>> - else if (priv_stack_mode == PRIV_STACK_SUB_PROG && orig_stack_depth)
>> + if (priv_stack_mode == PRIV_STACK_ROOT_PROG) {
>> + int offs;
>> + u8 *func;
>> +
>> + if (!bpf_prog->aux->has_prog_call) {
>> + emit_root_priv_frame_ptr(&prog, bpf_prog, orig_stack_depth);
>> + } else {
>> + EMIT1(0x57); /* push rdi */
>> + if (is_subprog) {
>> + /* subprog may have up to 5 arguments */
>> + EMIT1(0x56); /* push rsi */
>> + EMIT1(0x52); /* push rdx */
>> + EMIT1(0x51); /* push rcx */
>> + EMIT2(0x41, 0x50); /* push r8 */
>> + }
>> + emit_mov_imm64(&prog, BPF_REG_1, (long) bpf_prog >> 32,
>> + (u32) (long) bpf_prog);
>> + func = (u8 *)__bpf_prog_enter_recur_limited;
>> + offs = prog - temp;
>> + offs += x86_call_depth_emit_accounting(&prog, func, image + offs);
>> + emit_call(&prog, func, image + offs);
>> + if (is_subprog) {
>> + EMIT2(0x41, 0x58); /* pop r8 */
>> + EMIT1(0x59); /* pop rcx */
>> + EMIT1(0x5a); /* pop rdx */
>> + EMIT1(0x5e); /* pop rsi */
>> + }
>> + EMIT1(0x5f); /* pop rdi */
>> +
>> + EMIT4(0x48, 0x83, 0xf8, 0x0); /* cmp rax,0x0 */
>> + EMIT2(X86_JNE, num_bytes_of_emit_return() + 1);
>> +
>> + /* return if stack recursion has been reached */
>> + EMIT1(0xC9); /* leave */
>> + emit_return(&prog, image + (prog - temp));
>> +
>> + /* cnt -= 1 */
>> + emit_alu_helper_1(&prog, BPF_ALU64 | BPF_SUB | BPF_K,
>> + BPF_REG_0, 1);
>> +
>> + /* accum_stack_depth = cnt * subtree_stack_depth */
>> + emit_alu_helper_3(&prog, BPF_ALU64 | BPF_MUL | BPF_K, BPF_REG_0,
>> + bpf_prog->aux->subtree_stack_depth);
>> +
>> + emit_root_priv_frame_ptr(&prog, bpf_prog, orig_stack_depth);
>> +
>> + /* r9 += accum_stack_depth */
>> + emit_alu_helper_2(&prog, BPF_ALU64 | BPF_ADD | BPF_X, X86_REG_R9,
>> + BPF_REG_0);
> That's way too much asm for logic that can stay in C.
>
> bpf_trampoline_enter() should select __bpf_prog_enter_recur_limited()
> for appropriate prog_type/attach_type/etc.
The above jit code not just for the main prog, but also for callback fn's
since callback fn could call bpf prog as well. So putting in bpf trampoline
not enough.
But I can improve the above by putting the most logic
cnt -= 1; accum_stack_depth = cnt * subtree_stack_depth; r9 += accum_stack_depth
inside __bpf_prog_enter_recur_limited().
>
> JITs don't need to change.
next prev parent reply other threads:[~2024-10-11 4:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-10 17:55 [PATCH bpf-next v4 00/10] bpf: Support private stack for bpf progs Yonghong Song
2024-10-10 17:55 ` [PATCH bpf-next v4 01/10] bpf: Allow each subprog having stack size of 512 bytes Yonghong Song
2024-10-10 17:56 ` [PATCH bpf-next v4 02/10] bpf: Mark each subprog with proper private stack modes Yonghong Song
2024-10-10 17:56 ` [PATCH bpf-next v4 03/10] bpf, x86: Refactor func emit_prologue Yonghong Song
2024-10-10 17:56 ` [PATCH bpf-next v4 04/10] bpf, x86: Create a helper for certain "reg <op>= imm" operations Yonghong Song
2024-10-10 17:56 ` [PATCH bpf-next v4 05/10] bpf, x86: Add jit support for private stack Yonghong Song
2024-10-10 17:56 ` [PATCH bpf-next v4 06/10] selftests/bpf: Add private stack tests Yonghong Song
2024-10-10 17:56 ` [PATCH bpf-next v4 07/10] bpf: Support calling non-tailcall bpf prog Yonghong Song
2024-10-10 20:28 ` Alexei Starovoitov
2024-10-11 4:12 ` Yonghong Song
2024-10-15 21:18 ` Tejun Heo
2024-10-15 21:35 ` Alexei Starovoitov
2024-10-10 17:56 ` [PATCH bpf-next v4 08/10] bpf, x86: Create two helpers for some arith operations Yonghong Song
2024-10-10 20:21 ` Alexei Starovoitov
2024-10-11 4:16 ` Yonghong Song
2024-10-10 17:56 ` [PATCH bpf-next v4 09/10] bpf, x86: Jit support for nested bpf_prog_call Yonghong Song
2024-10-10 20:53 ` Alexei Starovoitov
2024-10-11 4:20 ` Yonghong Song [this message]
2024-10-11 4:29 ` Alexei Starovoitov
2024-10-11 15:38 ` Yonghong Song
2024-10-11 15:40 ` Alexei Starovoitov
2024-10-11 16:14 ` Yonghong Song
2024-10-10 17:56 ` [PATCH bpf-next v4 10/10] selftests/bpf: Add tests for bpf_prog_call() Yonghong Song
2024-10-15 21:28 ` [PATCH bpf-next v4 00/10] bpf: Support private stack for bpf progs Tejun Heo
2024-10-15 21:39 ` Alexei Starovoitov
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=64da4fb8-7e13-41fc-891e-c0f79bf778d1@linux.dev \
--to=yonghong.song@linux.dev \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=martin.lau@kernel.org \
--cc=tj@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