From: Eduard Zingerman <eddyz87@gmail.com>
To: Yonghong Song <yonghong.song@linux.dev>,
bpf@vger.kernel.org, ast@kernel.org
Cc: andrii@kernel.org, daniel@iogearbox.net, martin.lau@linux.dev,
kernel-team@fb.com
Subject: Re: [PATCH bpf-next 1/3] bpf: support nocsr patterns for calls to kfuncs
Date: Tue, 13 Aug 2024 00:55:11 -0700 [thread overview]
Message-ID: <b7518fdfd0a01f1eef66556b62f5e72484501eae.camel@gmail.com> (raw)
In-Reply-To: <2ca49adc-2c90-42ee-b1ff-bf339731ad5a@linux.dev>
On Mon, 2024-08-12 at 22:36 -0700, Yonghong Song wrote:
[...]
> > @@ -16140,6 +16140,28 @@ static bool verifier_inlines_helper_call(struct bpf_verifier_env *env, s32 imm)
> > }
> > }
> >
> > +/* Same as helper_nocsr_clobber_mask() but for kfuncs, see comment above */
> > +static u32 kfunc_nocsr_clobber_mask(struct bpf_kfunc_call_arg_meta *meta)
> > +{
> > + const struct btf_param *params;
> > + u32 vlen, i, mask;
>
> In helper_nocsr_clobber_mask, we have u8 mask. To be consistent, can we have 'u8 mask' here?
> Are you worried that the number of arguments could be more than 7? This seems not the case
> right now.
Before the nocsr part for helpers landed there was a change request to
make helper_nocsr_clobber_mask() return u32. I modified the function
but forgot to change the type for 'mask' local variable.
The main point in using u32 is uniformity.
I can either change kfunc_nocsr_clobber_mask() to use u8 for mask,
or update helper_nocsr_clobber_mask() to use u32 for mask.
>
> > +
> > + params = btf_params(meta->func_proto);
> > + vlen = btf_type_vlen(meta->func_proto);
> > + mask = 0;
> > + if (!btf_type_is_void(btf_type_by_id(meta->btf, meta->func_proto->type)))
> > + mask |= BIT(BPF_REG_0);
> > + for (i = 0; i < vlen; ++i)
> > + mask |= BIT(BPF_REG_1 + i);
> > + return mask;
> > +}
> > +
> > +/* Same as verifier_inlines_helper_call() but for kfuncs, see comment above */
> > +static bool verifier_inlines_kfunc_call(struct bpf_kfunc_call_arg_meta *meta)
> > +{
> > + return false;
> > +}
> > +
> > /* GCC and LLVM define a no_caller_saved_registers function attribute.
> > * This attribute means that function scratches only some of
> > * the caller saved registers defined by ABI.
> > @@ -16238,6 +16260,20 @@ static void mark_nocsr_pattern_for_call(struct bpf_verifier_env *env,
> > bpf_jit_inlines_helper_call(call->imm));
> > }
> >
> > + if (bpf_pseudo_kfunc_call(call)) {
> > + struct bpf_kfunc_call_arg_meta meta;
> > + int err;
> > +
> > + err = fetch_kfunc_meta(env, call, &meta, NULL);
> > + if (err < 0)
> > + /* error would be reported later */
> > + return;
> > +
> > + clobbered_regs_mask = kfunc_nocsr_clobber_mask(&meta);
> > + can_be_inlined = (meta.kfunc_flags & KF_NOCSR) &&
> > + verifier_inlines_kfunc_call(&meta);
>
> I think we do not need both meta.kfunc_flags & KF_NOCSR and
> verifier_inlines_kfunc_call(&meta). Only one of them is enough
> since they test very similar thing. You do need to ensure
> kfuncs with KF_NOCSR in special_kfunc_list though.
> WDYT?
I can remove the flag in favour of verifier_inlines_kfunc_call().
>
> > + }
> > +
> > if (clobbered_regs_mask == ALL_CALLER_SAVED_REGS)
> > return;
> >
next prev parent reply other threads:[~2024-08-13 7:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 23:43 [PATCH bpf-next 0/3] support nocsr patterns for calls to kfuncs Eduard Zingerman
2024-08-12 23:43 ` [PATCH bpf-next 1/3] bpf: " Eduard Zingerman
2024-08-13 5:36 ` Yonghong Song
2024-08-13 7:55 ` Eduard Zingerman [this message]
2024-08-13 15:18 ` Yonghong Song
2024-08-13 18:57 ` Eduard Zingerman
2024-08-15 21:24 ` Andrii Nakryiko
2024-08-15 22:07 ` Eduard Zingerman
2024-08-15 22:23 ` Yonghong Song
2024-08-15 22:29 ` Eduard Zingerman
2024-08-15 22:16 ` Yonghong Song
2024-08-15 22:22 ` Yonghong Song
2024-08-12 23:43 ` [PATCH bpf-next 2/3] bpf: mark bpf_cast_to_kern_ctx and bpf_rdonly_cast as KF_NOCSR Eduard Zingerman
2024-08-15 21:25 ` Andrii Nakryiko
2024-08-15 21:59 ` Eduard Zingerman
2024-08-15 22:12 ` Andrii Nakryiko
2024-08-15 22:14 ` Eduard Zingerman
2024-08-12 23:43 ` [PATCH bpf-next 3/3] selftests/bpf: check if nocsr pattern is recognized for kfuncs Eduard Zingerman
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=b7518fdfd0a01f1eef66556b62f5e72484501eae.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=martin.lau@linux.dev \
--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