[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Z6FtkchYQjgjdv1x@google.com>
Date: Tue, 4 Feb 2025 01:29:53 +0000
From: Peilin Ye <yepeilin@...gle.com>
To: Eduard Zingerman <eddyz87@...il.com>
Cc: bpf@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, bpf@...f.org,
Xu Kuohai <xukuohai@...weicloud.com>,
David Vernet <void@...ifault.com>,
Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Andrii Nakryiko <andrii@...nel.org>,
Martin KaFai Lau <martin.lau@...ux.dev>, Song Liu <song@...nel.org>,
Yonghong Song <yonghong.song@...ux.dev>,
John Fastabend <john.fastabend@...il.com>,
KP Singh <kpsingh@...nel.org>, Stanislav Fomichev <sdf@...ichev.me>,
Hao Luo <haoluo@...gle.com>, Jiri Olsa <jolsa@...nel.org>,
Jonathan Corbet <corbet@....net>,
"Paul E. McKenney" <paulmck@...nel.org>,
Puranjay Mohan <puranjay@...nel.org>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>, Quentin Monnet <qmo@...nel.org>,
Mykola Lysenko <mykolal@...com>, Shuah Khan <shuah@...nel.org>,
Josh Don <joshdon@...gle.com>, Barret Rhoden <brho@...gle.com>,
Neel Natu <neelnatu@...gle.com>,
Benjamin Segall <bsegall@...gle.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH bpf-next v1 7/8] selftests/bpf: Add selftests for
load-acquire and store-release instructions
On Mon, Feb 03, 2025 at 04:52:52PM -0800, Eduard Zingerman wrote:
> > > > --- a/tools/testing/selftests/bpf/progs/arena_atomics.c
> > > > +++ b/tools/testing/selftests/bpf/progs/arena_atomics.c
> > > [...]
> > >
> > > > +SEC("raw_tp/sys_enter")
> > > > +int load_acquire(const void *ctx)
> > > > +{
> > > > + if (pid != (bpf_get_current_pid_tgid() >> 32))
> > > > + return 0;
> > >
> > > Nit: This check is not needed, since bpf_prog_test_run_opts() is used
> > > to run the tests.
> >
> > Could you explain a bit more why it's not needed?
> >
> > I read commit 0f4feacc9155 ("selftests/bpf: Adding pid filtering for
> > atomics test") which added those 'pid' checks to atomics/ tests. The
> > commit message [1] says the purpose was to "make atomics test able to
> > run in parallel with other tests", which I couldn't understand.
> >
> > How using bpf_prog_test_run_opts() makes those 'pid' checks unnecessary?
> >
> > [1] https://lore.kernel.org/bpf/20211006185619.364369-11-fallentree@fb.com/#r
>
> Hi Peilin,
>
> The entry point for the test looks as follows:
>
> void test_arena_atomics(void)
> {
> ...
> skel = arena_atomics__open();
> if (!ASSERT_OK_PTR(skel, "arena atomics skeleton open"))
> return;
>
> if (skel->data->skip_tests) { ... }
> err = arena_atomics__load(skel);
> if (!ASSERT_OK(err, "arena atomics skeleton load"))
> return;
> skel->bss->pid = getpid();
>
> if (test__start_subtest("add"))
> test_add(skel);
> ...
>
> cleanup:
> arena_atomics__destroy(skel);
> }
>
> Note arena_atomics__{open,load} calls but absence of the
> arena_atomics__attach call. W/o arena_atomics__attach call the
> programs would not be hooked to the designated extension points,
> e.g. "raw_tp/sys_enter".
>
> The bpf_prog_test_run_opts() invokes BPF_PROG_TEST_RUN command of the
> bpf system call, which does not attach the program either,
> but executes jitted code directly with fake context.
> (See bpf_prog_ops->test_run callback (method?) and
> bpf_prog_test_run_raw_tp()).
>
> Same happens in prog{,_tests}/arena.c: no attachment happens after
> commit [2]. Commit [1] is unnecessary after [2].
>
> [2] commit 04fcb5f9a104 ("selftests/bpf: Migrate from bpf_prog_test_run")
I see. Thanks for the quick reply as always!
Peilin Ye
Powered by blists - more mailing lists