From: Menglong Dong <menglong.dong@linux.dev>
To: Menglong Dong <menglong8.dong@gmail.com>,
ast@kernel.org, Eduard Zingerman <eddyz87@gmail.com>
Cc: daniel@iogearbox.net, john.fastabend@gmail.com,
andrii@kernel.org, martin.lau@linux.dev, song@kernel.org,
yonghong.song@linux.dev, kpsingh@kernel.org, sdf@fomichev.me,
haoluo@google.com, jolsa@kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v5 2/2] selftests/bpf: test the jited inline of bpf_get_current_task
Date: Tue, 20 Jan 2026 09:27:46 +0800 [thread overview]
Message-ID: <5212176.31r3eYUQgx@7950hx> (raw)
In-Reply-To: <0a277a7ff97395803d114a0ea74a5cab9fd75237.camel@gmail.com>
On 2026/1/20 04:37, Eduard Zingerman wrote:
> On Mon, 2026-01-19 at 15:02 +0800, Menglong Dong wrote:
> > Add the testcase for the jited inline of bpf_get_current_task().
> >
> > Signed-off-by: Menglong Dong <dongml2@chinatelecom.cn>
> > ---
> > .../selftests/bpf/prog_tests/verifier.c | 2 ++
> > .../selftests/bpf/progs/verifier_jit_inline.c | 35 +++++++++++++++++++
> > 2 files changed, 37 insertions(+)
> > create mode 100644 tools/testing/selftests/bpf/progs/verifier_jit_inline.c
> >
> > diff --git a/tools/testing/selftests/bpf/prog_tests/verifier.c b/tools/testing/selftests/bpf/prog_tests/verifier.c
> > index 38c5ba70100c..2ae7b096bd64 100644
> > --- a/tools/testing/selftests/bpf/prog_tests/verifier.c
> > +++ b/tools/testing/selftests/bpf/prog_tests/verifier.c
> > @@ -111,6 +111,7 @@
> > #include "verifier_xdp_direct_packet_access.skel.h"
> > #include "verifier_bits_iter.skel.h"
> > #include "verifier_lsm.skel.h"
> > +#include "verifier_jit_inline.skel.h"
> > #include "irq.skel.h"
> >
> > #define MAX_ENTRIES 11
> > @@ -253,6 +254,7 @@ void test_verifier_bits_iter(void) { RUN(verifier_bits_iter); }
> > void test_verifier_lsm(void) { RUN(verifier_lsm); }
> > void test_irq(void) { RUN(irq); }
> > void test_verifier_mtu(void) { RUN(verifier_mtu); }
> > +void test_verifier_jit_inline(void) { RUN(verifier_jit_inline); }
> >
> > static int init_test_val_map(struct bpf_object *obj, char *map_name)
> > {
> > diff --git a/tools/testing/selftests/bpf/progs/verifier_jit_inline.c b/tools/testing/selftests/bpf/progs/verifier_jit_inline.c
> > new file mode 100644
> > index 000000000000..0938ca1dac87
> > --- /dev/null
> > +++ b/tools/testing/selftests/bpf/progs/verifier_jit_inline.c
> > @@ -0,0 +1,35 @@
> > +// SPDX-License-Identifier: GPL-2.0
> > +
> > +#include <vmlinux.h>
> > +#include <bpf/bpf_helpers.h>
> > +#include "bpf_misc.h"
> > +
> > +#if defined(__TARGET_ARCH_x86) || defined(__TARGET_ARCH_arm64)
>
> I don't think this #if is necessary as well as 'dummy_test'.
> test_loader.c:run_subtest() checks current architecture against a mask
> supplied by __arch_* annotations and skips the test for unsupported
> archs.
Yeah, you are right, they are unnecessary.
>
> > +
> > +SEC("fentry/bpf_fentry_test1")
> > +__description("Jit inline, bpf_get_current_task")
>
> Nit: please don't use __description() for new tests,
> it makes "./test_progs -t" tests selection harder.
OK, I'll remove them.
Thanks!
Menglong Dong
>
> > +__success __retval(0)
> > +__arch_x86_64
> > +__jited(" addq %gs:{{.*}}, %rax")
> > +__arch_arm64
> > +__jited(" mrs x7, SP_EL0")
> > +int inline_bpf_get_current_task(void)
> > +{
> > + bpf_get_current_task();
> > +
> > + return 0;
> > +}
> > +
> > +#else
> > +
> > +SEC("kprobe")
> > +__description("Jit inline is not supported, use a dummy test")
> > +__success
> > +int dummy_test(void)
> > +{
> > + return 0;
> > +}
> > +
> > +#endif
> > +
> > +char _license[] SEC("license") = "GPL";
>
>
prev parent reply other threads:[~2026-01-20 1:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 7:02 [PATCH bpf-next v5 0/2] bpf, x86: inline bpf_get_current_task() for x86_64 Menglong Dong
2026-01-19 7:02 ` [PATCH bpf-next v5 1/2] " Menglong Dong
2026-01-19 20:43 ` Eduard Zingerman
2026-01-19 7:02 ` [PATCH bpf-next v5 2/2] selftests/bpf: test the jited inline of bpf_get_current_task Menglong Dong
2026-01-19 20:37 ` Eduard Zingerman
2026-01-20 1:27 ` Menglong Dong [this message]
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=5212176.31r3eYUQgx@7950hx \
--to=menglong.dong@linux.dev \
--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
all inboxes | Powered by JetHome®