From: zf <zf15750701@gmail.com>
To: Menglong Dong <menglong8.dong@gmail.com>,
Andrii Nakryiko <andrii.nakryiko@gmail.com>,
Alan Maguire <alan.maguire@oracle.com>
Cc: bpf <bpf@vger.kernel.org>
Subject: Re: bpf: add support to check kernel features in BPF program
Date: Fri, 5 May 2023 15:51:42 +0800 [thread overview]
Message-ID: <c9543049-ef85-88da-5c55-42bed4819c5d@gmail.com> (raw)
In-Reply-To: <CADxym3ax73kYEyJMZwN+bTwmX9VhZ3WJe+wC9RGGwpfdjLdf3g@mail.gmail.com>
在 2023/5/4 19:09, Menglong Dong 写道:
> Hello,
>
> I find that it's not supported yet to check if the bpf features are
> supported by the target kernel in the BPF program, which makes
> it hard to keep the BPF program compatible with different kernel
> versions.
>
> For example, I want to use the helper bpf_jiffies64(), but I am not
> sure if it is supported by the target, as my program can run in
> kernel 5.4 or kernel 5.10. Therefore, I have to compile two versions
> BPF elf and load one of them according to the current kernel version.
> The part of BPF program can be this:
>
> #ifdef BPF_FEATS_JIFFIES64
> jiffies = bpf_jiffies64();
> #else
> jiffies = 0;
> #endif
>
> And I will generate xxx_no_jiffies.skel.h and xxx_jiffies.skel.h
> with -DBPF_FEATS_JIFFIES64 or not.
>
> This method is too silly, as I have to compile 8(2*2*2) versions of
> the BPF program if I am not sure if 3 bpf helpers are supported by the
> target kernel.
>
> Therefore, I think it may be helpful if we can check if the helpers
> are support like this:
>
> if (bpf_core_helper_exist(bpf_jiffies64))
> jiffies = bpf_jiffies64();
> else
> jiffies = 0;
>
> And bpf_core_helper_exist() can be defined like this:
>
> #define bpf_core_helper_exist(helper) \
> __builtin_preserve_helper_info(helper, BPF_HELPER_EXISTS)
>
> Besides, in order to prevent the verifier from checking the helper
> that is not supported, we need to remove the dead code in libbpf.
> As the kernel already has the ability to remove dead and nop insn,
> we can just make the dead insn to nop.
>
> Another option is to make the BPF program support "const value".
> Such const values can be rewrite before load, the dead code can
> be removed. For example:
>
> #define bpf_const_value __attribute__((preserve_const_value))
>
> bpf_const_value bool is_bpf_jiffies64_supported = 0;
>
> if (is_bpf_jiffies64_supported)
> jiffies = bpf_jiffies64();
> else
> jiffies = 0;
>
> The 'is_bpf_jiffies64_supported' will be compiled to an imm, and
> can be rewrite and relocated through libbpf by the user. Then, we
> can make the dead insn 'nop'.
>
> What do you think? I'm not sure if these methods work and want
> to get some advice before coding.
>
> Thanks!
> Menglong Dong
Maybe you can use like this
bpf_core_enum_value_exists(enum bpf_func_id, BPF_FUNC_jiffies64);
prev parent reply other threads:[~2023-05-05 7:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 11:09 bpf: add support to check kernel features in BPF program Menglong Dong
2023-05-04 16:53 ` Yonghong Song
2023-05-05 2:42 ` Menglong Dong
2023-05-05 4:12 ` Andrii Nakryiko
2023-05-05 6:54 ` Menglong Dong
2023-05-05 16:58 ` Andrii Nakryiko
2023-05-06 2:45 ` Menglong Dong
2023-05-05 7:51 ` zf [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=c9543049-ef85-88da-5c55-42bed4819c5d@gmail.com \
--to=zf15750701@gmail.com \
--cc=alan.maguire@oracle.com \
--cc=andrii.nakryiko@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=menglong8.dong@gmail.com \
/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