From: Leon Hwang <leon.hwang@linux.dev>
To: bpf@vger.kernel.org
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
jolsa@kernel.org, eddyz87@gmail.com, leon.hwang@linux.dev,
kernel-patches-bot@fb.com
Subject: [PATCH bpf-next 0/2] bpf, x64: Introduce two tailcall enhancements
Date: Mon, 21 Oct 2024 21:39:27 +0800 [thread overview]
Message-ID: <20241021133929.67782-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 to a subprog only if the subprog is
tail_call_reachable.
2. Tailcall info is propagated through the trampoline only when the target
is a subprog and it is tail_call_reachable.
Leon Hwang (2):
bpf, x64: Propagate tailcall info only for tail_call_reachable
subprogs
bpf, verifier: Check trampoline attach target is tail_call_reachable
subprog
arch/x86/net/bpf_jit_comp.c | 4 +++-
include/linux/bpf.h | 1 +
kernel/bpf/verifier.c | 10 +++++++++-
3 files changed, 13 insertions(+), 2 deletions(-)
--
2.44.0
next reply other threads:[~2024-10-21 13:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-21 13:39 Leon Hwang [this message]
2024-10-21 13:39 ` [PATCH bpf-next 1/2] bpf, x64: Propagate tailcall info only for tail_call_reachable subprogs Leon Hwang
2024-10-21 17:49 ` Yonghong Song
2024-10-22 1:46 ` Leon Hwang
2024-10-24 2:29 ` Yonghong Song
2024-10-24 3:33 ` Leon Hwang
2024-10-24 16:38 ` Yonghong Song
2024-10-24 16:56 ` Yonghong Song
2024-10-24 17:01 ` Yonghong Song
2024-10-24 22:09 ` Alexei Starovoitov
2024-10-25 2:37 ` Leon Hwang
2024-10-21 13:39 ` [PATCH bpf-next 2/2] bpf, verifier: Check trampoline target is tail_call_reachable subprog Leon Hwang
2024-10-24 2:46 ` Yonghong Song
-- strict thread matches above, loose matches on Subject: below --
2024-10-28 13:40 [PATCH bpf-next 0/2] bpf, x64: Introduce two tailcall enhancements Leon Hwang
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=20241021133929.67782-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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.