[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAADnVQKnyz4gqDXfo0OTDuGGbn3i-+roB4M4Q-uxiMLrSP=S=g@mail.gmail.com>
Date: Mon, 23 Jan 2023 21:32:03 -0800
From: Alexei Starovoitov <alexei.starovoitov@...il.com>
To: David Vernet <void@...ifault.com>
Cc: bpf <bpf@...r.kernel.org>, 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 <yhs@...a.com>,
John Fastabend <john.fastabend@...il.com>,
KP Singh <kpsingh@...nel.org>,
Stanislav Fomichev <sdf@...gle.com>,
Hao Luo <haoluo@...gle.com>, Jiri Olsa <jolsa@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
Kernel Team <kernel-team@...a.com>, Tejun Heo <tj@...nel.org>,
Kumar Kartikeya Dwivedi <memxor@...il.com>
Subject: Re: [PATCH bpf-next 3/3] bpf/selftests: Verify struct_ops prog
sleepable behavior
On Mon, Jan 23, 2023 at 3:22 PM David Vernet <void@...ifault.com> wrote:
>
> +static struct dummy_st_ops *open_load_skel(void)
> +{
> + int err;
> + struct dummy_st_ops *skel;
> +
> + skel = dummy_st_ops__open();
> + if (!ASSERT_OK_PTR(skel, "dummy_st_ops_open"))
> + return NULL;
> +
> + err = bpf_program__set_flags(skel->progs.test_3, BPF_F_SLEEPABLE);
Feels that this is incomplete without libbpf support.
Instead of:
+SEC("struct_ops/test_3")
the users should be able to:
+SEC("struct_ops.s/test_3")
and the above manual set_flags won't be needed.
Powered by blists - more mailing lists