public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: Leon Hwang <leon.hwang@linux.dev>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: bpf <bpf@vger.kernel.org>, Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Andrii Nakryiko <andrii@kernel.org>,
	Yonghong Song <yonghong.song@linux.dev>,
	Jiri Olsa <jolsa@kernel.org>, Eddy Z <eddyz87@gmail.com>,
	kernel-patches-bot@fb.com
Subject: Re: [PATCH bpf-next v3 1/2] bpf, x64: Propagate tailcall info only for subprogs
Date: Wed, 13 Nov 2024 09:53:55 +0800	[thread overview]
Message-ID: <5e7643ba-ae62-4ca8-86b1-fcfb706148c6@linux.dev> (raw)
In-Reply-To: <CAADnVQLvt3T5X3wev2fZ1pvwqzJ0_tB-DXxTdBp8GOo+DP_c9Q@mail.gmail.com>



On 13/11/24 09:31, Alexei Starovoitov wrote:
> On Thu, Nov 7, 2024 at 5:46 AM Leon Hwang <leon.hwang@linux.dev> wrote:
>>
>> In x64 JIT, propagate tailcall info only for subprogs, not for helpers
>> or kfuncs.
>>
>> Acked-by: Yonghong Song <yonghong.song@linux.dev>
>> Signed-off-by: Leon Hwang <leon.hwang@linux.dev>
>> ---
>>  arch/x86/net/bpf_jit_comp.c | 3 ++-
>>  1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/arch/x86/net/bpf_jit_comp.c b/arch/x86/net/bpf_jit_comp.c
>> index 06b080b61aa57..eb08cc6d66401 100644
>> --- a/arch/x86/net/bpf_jit_comp.c
>> +++ b/arch/x86/net/bpf_jit_comp.c
>> @@ -2124,10 +2124,11 @@ st:                     if (is_imm8(insn->off))
>>
>>                         /* call */
>>                 case BPF_JMP | BPF_CALL: {
>> +                       bool pseudo_call = src_reg == BPF_PSEUDO_CALL;
>>                         u8 *ip = image + addrs[i - 1];
>>
>>                         func = (u8 *) __bpf_call_base + imm32;
>> -                       if (tail_call_reachable) {
>> +                       if (pseudo_call && tail_call_reachable) {
>>                                 LOAD_TAIL_CALL_CNT_PTR(bpf_prog->aux->stack_depth);
>>                                 ip += 7;
>>                         }
> 
> I've applied this patch with this tweak:
> if (src_reg == BPF_PSEUDO_CALL && tail_call_reachable)
> 
> I don't see much value in patch 2.
> The tail_call feature is an old approach. It is now causing
> maintenance issues with other features.
> I'd rather not touch anything tail call related.
> So I dropped patch 2.
> 
> I'd like to see proper indirect goto and indirect call
> support being developed further.
> Anton started working on it, but dropped the ball.
> We need to commandeer the patches.

Great to see jmp table supporting tail call.

Thanks,
Leon



  reply	other threads:[~2024-11-13  1:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-07 13:45 [PATCH bpf-next v3 0/2] bpf, x64: Introduce two tailcall enhancements Leon Hwang
2024-11-07 13:45 ` [PATCH bpf-next v3 1/2] bpf, x64: Propagate tailcall info only for subprogs Leon Hwang
2024-11-13  1:31   ` Alexei Starovoitov
2024-11-13  1:53     ` Leon Hwang [this message]
2024-11-13  2:14     ` Anton Protopopov
2024-11-13  2:15       ` Alexei Starovoitov
2024-11-07 13:45 ` [PATCH bpf-next v3 2/2] bpf, verifier: Check trampoline target is tail_call_reachable subprog Leon Hwang
2024-11-13  1:40 ` [PATCH bpf-next v3 0/2] bpf, x64: Introduce two tailcall enhancements patchwork-bot+netdevbpf

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=5e7643ba-ae62-4ca8-86b1-fcfb706148c6@linux.dev \
    --to=leon.hwang@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=eddyz87@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kernel-patches-bot@fb.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