From: Leon Hwang <leon.hwang@linux.dev>
To: bpf@vger.kernel.org
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
yonghong.song@linux.dev, jolsa@kernel.org, eddyz87@gmail.com,
leon.hwang@linux.dev, kernel-patches-bot@fb.com
Subject: [PATCH bpf-next v3 0/2] bpf, x64: Introduce two tailcall enhancements
Date: Thu, 7 Nov 2024 21:45:27 +0800 [thread overview]
Message-ID: <20241107134529.8602-1-leon.hwang@linux.dev> (raw)
This patch set introduces two enhancements aimed at improving tailcall
handling in the x64 JIT:
1. Tailcall info is propagated only for subprogs.
2. Tailcall info is propagated through the trampoline only when the target
is a subprog and it is tail_call_reachable.
Changes:
v2 -> v3:
* Add Yonghong's ACK.
v1 -> v2:
* Address comment from Alexei:
* Rather live with tail call inefficiency than abuse insns fields
further.
Leon Hwang (2):
bpf, x64: Propagate tailcall info only for subprogs
bpf, verifier: Check trampoline target is tail_call_reachable subprog
arch/x86/net/bpf_jit_comp.c | 3 ++-
include/linux/bpf.h | 1 +
kernel/bpf/verifier.c | 4 +++-
3 files changed, 6 insertions(+), 2 deletions(-)
--
2.44.0
next reply other threads:[~2024-11-07 13:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 13:45 Leon Hwang [this message]
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
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=20241107134529.8602-1-leon.hwang@linux.dev \
--to=leon.hwang@linux.dev \
--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