From: Menglong Dong <menglong.dong@linux.dev>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Menglong Dong <menglong8.dong@gmail.com>,
Alexei Starovoitov <ast@kernel.org>, Eduard <eddyz87@gmail.com>,
Daniel Borkmann <daniel@iogearbox.net>,
John Fastabend <john.fastabend@gmail.com>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@fomichev.me>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>, bpf <bpf@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH bpf-next v4 1/2] bpf, x86: inline bpf_get_current_task() for x86_64
Date: Wed, 14 Jan 2026 09:33:07 +0800 [thread overview]
Message-ID: <2396904.ElGaqSPkdT@7940hx> (raw)
In-Reply-To: <CAADnVQ+Q2m19+rMLXbq98uobL6Zy5yKceDiw-PAmrmCSvvjHaw@mail.gmail.com>
On 2026/1/14 09:24 Alexei Starovoitov <alexei.starovoitov@gmail.com> write:
> On Tue, Jan 13, 2026 at 5:19 PM Menglong Dong <menglong.dong@linux.dev> wrote:
> >
> > On 2026/1/14 01:50 Alexei Starovoitov <alexei.starovoitov@gmail.com> write:
> > > On Mon, Jan 12, 2026 at 2:45 AM Menglong Dong <menglong8.dong@gmail.com> wrote:
> > > >
> > > > Inline bpf_get_current_task() and bpf_get_current_task_btf() for x86_64
> > > > to obtain better performance.
> > > >
> > > > In !CONFIG_SMP case, the percpu variable is just a normal variable, and
> > > > we can read the current_task directly.
> > > >
> > > > Signed-off-by: Menglong Dong <dongml2@chinatelecom.cn>
> > > > ---
> > > > v4:
> > > > - handle the !CONFIG_SMP case
> > > >
> > > > v3:
> > > > - implement it in the verifier with BPF_MOV64_PERCPU_REG() instead of in
> > > > x86_64 JIT.
> > > > ---
> > > > kernel/bpf/verifier.c | 29 +++++++++++++++++++++++++++++
> > > > 1 file changed, 29 insertions(+)
> > > >
> > > > diff --git a/kernel/bpf/verifier.c b/kernel/bpf/verifier.c
> > > > index 3d44c5d06623..12e99171afd8 100644
> > > > --- a/kernel/bpf/verifier.c
> > > > +++ b/kernel/bpf/verifier.c
> > > > @@ -17688,6 +17688,8 @@ static bool verifier_inlines_helper_call(struct bpf_verifier_env *env, s32 imm)
> > > > switch (imm) {
> > > > #ifdef CONFIG_X86_64
> > > > case BPF_FUNC_get_smp_processor_id:
> > > > + case BPF_FUNC_get_current_task_btf:
> > > > + case BPF_FUNC_get_current_task:
> > > > return env->prog->jit_requested && bpf_jit_supports_percpu_insn();
> > > > #endif
> > > > default:
> > > > @@ -23273,6 +23275,33 @@ static int do_misc_fixups(struct bpf_verifier_env *env)
> > > > insn = new_prog->insnsi + i + delta;
> > > > goto next_insn;
> > > > }
> > > > +
> > > > + /* Implement bpf_get_current_task() and bpf_get_current_task_btf() inline. */
> > > > + if ((insn->imm == BPF_FUNC_get_current_task || insn->imm == BPF_FUNC_get_current_task_btf) &&
> > > > + verifier_inlines_helper_call(env, insn->imm)) {
> > >
> > > Though verifier_inlines_helper_call() gates this with CONFIG_X86_64,
> > > I think we still need explicit:
> > > #if defined(CONFIG_X86_64) && !defined(CONFIG_UML)
> > >
> > > just like we did for BPF_FUNC_get_smp_processor_id.
> > > Please check. I suspect UML will break without it.
> >
> > Do you mean that we need to use
> > #if defined(CONFIG_X86_64) && !defined(CONFIG_UML)
> > here?
> >
> > The whole code is already within it. You can have a look up:
> >
> > #if defined(CONFIG_X86_64) && !defined(CONFIG_UML)
> > /* Implement bpf_get_smp_processor_id() inline. */
> > if (insn->imm == BPF_FUNC_get_smp_processor_id &&
> > verifier_inlines_helper_call(env, insn->imm)) {
> > [......]
> > /* Implement bpf_get_current_task() and bpf_get_current_task_btf() inline. */
> > if ((insn->imm == BPF_FUNC_get_current_task || insn->imm == BPF_FUNC_get_current_task_btf) &&
> > verifier_inlines_helper_call(env, insn->imm)) {
> > [......]
> > #endif
>
> oh. I see. I misread it as '+#endif' (with a +) and assumed
> it's part of new code.
>
> >
> > >
> > > > +#ifdef CONFIG_SMP
> > > > + insn_buf[0] = BPF_MOV64_IMM(BPF_REG_0, (u32)(unsigned long)¤t_task);
> > > > + insn_buf[1] = BPF_MOV64_PERCPU_REG(BPF_REG_0, BPF_REG_0);
> > > > + insn_buf[2] = BPF_LDX_MEM(BPF_DW, BPF_REG_0, BPF_REG_0, 0);
> > > > +#else
> > > > + struct bpf_insn ld_current_addr[2] = {
> > > > + BPF_LD_IMM64(BPF_REG_0, (unsigned long)¤t_task)
> > > > + };
> > > > + insn_buf[0] = ld_current_addr[0];
> > > > + insn_buf[1] = ld_current_addr[1];
> > > > + insn_buf[2] = BPF_LDX_MEM(BPF_DW, BPF_REG_0, BPF_REG_0, 0);
> > > > +#endif
> > >
> > > I wouldn't bother with !SMP.
> > > If we need to add defined(CONFIG_X86_64) && !defined(CONFIG_UML)
> > > I would add && defined(CONFIG_SMP) to it.
> >
> > OK, let's skip the !SMP case to make the code more clear.
>
> Similar thoughts about your other patch where you introduce
> decl_tag to deal with different configs.
> For bpf CI we don't need to do such things.
> The kernel has to be configured with selftest/bpf/config.
> So doing extra work in test_progs to recognize !SMP looks like overkill.
You are right, and that's why I removed that patch in this version
after I realized this point.
Thanks!
Menglong Dong
next prev parent reply other threads:[~2026-01-14 1:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 10:45 [PATCH bpf-next v4 0/2] bpf, x86: inline bpf_get_current_task() for x86_64 Menglong Dong
2026-01-12 10:45 ` [PATCH bpf-next v4 1/2] " Menglong Dong
2026-01-13 17:50 ` Alexei Starovoitov
2026-01-14 1:19 ` Menglong Dong
2026-01-14 1:24 ` Alexei Starovoitov
2026-01-14 1:33 ` Menglong Dong [this message]
2026-01-12 10:45 ` [PATCH bpf-next v4 2/2] selftests/bpf: test the jited inline of bpf_get_current_task Menglong Dong
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=2396904.ElGaqSPkdT@7940hx \
--to=menglong.dong@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=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=menglong8.dong@gmail.com \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--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