From: Shuyi Cheng <chengshuyi@linux.alibaba.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>, Martin Lau <kafai@fb.com>,
Song Liu <songliubraving@fb.com>, Yonghong Song <yhs@fb.com>,
john fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Networking <netdev@vger.kernel.org>, bpf <bpf@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH bpf-next v4 1/3] libbpf: Introduce 'btf_custom_path' to 'bpf_obj_open_opts'
Date: Sat, 17 Jul 2021 09:15:50 +0800 [thread overview]
Message-ID: <0fa3b7f1-7928-eff9-1644-df3384171bcd@linux.alibaba.com> (raw)
In-Reply-To: <CAEf4BzawyyJ0hhvmSM8ba817VffOV2O3qG49fqh+VFseiixigA@mail.gmail.com>
On 7/16/21 12:51 PM, Andrii Nakryiko wrote:
> On Tue, Jul 13, 2021 at 5:43 AM Shuyi Cheng
> <chengshuyi@linux.alibaba.com> wrote:
>>
>> btf_custom_path allows developers to load custom BTF, and subsequent
>> CO-RE will use custom BTF for relocation.
>>
>> Learn from Andrii's comments in [0], add the btf_custom_path parameter
>> to bpf_obj_open_opts, you can directly use the skeleton's
>> <objname>_bpf__open_opts function to pass in the btf_custom_path
>> parameter.
>>
>> Prior to this, there was also a developer who provided a patch with
>> similar functions. It is a pity that the follow-up did not continue to
>> advance. See [1].
>>
>> [0]https://lore.kernel.org/bpf/CAEf4BzbJZLjNoiK8_VfeVg_Vrg=9iYFv+po-38SMe=UzwDKJ=Q@mail.gmail.com/#t
>> [1]https://yhbt.net/lore/all/CAEf4Bzbgw49w2PtowsrzKQNcxD4fZRE6AKByX-5-dMo-+oWHHA@mail.gmail.com/
>>
>> Signed-off-by: Shuyi Cheng <chengshuyi@linux.alibaba.com>
>> ---
>> tools/lib/bpf/libbpf.c | 36 ++++++++++++++++++++++++++++++------
>> tools/lib/bpf/libbpf.h | 9 ++++++++-
>> 2 files changed, 38 insertions(+), 7 deletions(-)
>>
>> diff --git a/tools/lib/bpf/libbpf.c b/tools/lib/bpf/libbpf.c
>> index 1e04ce7..6e11a7b 100644
>> --- a/tools/lib/bpf/libbpf.c
>> +++ b/tools/lib/bpf/libbpf.c
>> @@ -498,6 +498,13 @@ struct bpf_object {
>> * it at load time.
>> */
>> struct btf *btf_vmlinux;
>> + /* Path to the custom BTF to be used for BPF CO-RE relocations.
>> + * This custom BTF completely replaces the use of vmlinux BTF
>> + * for the purpose of CO-RE relocations.
>> + * NOTE: any other BPF feature (e.g., fentry/fexit programs,
>> + * struct_ops, etc) will need actual kernel BTF at /sys/kernel/btf/vmlinux.
>> + */
>
> this comment completely duplicates the one from bpf_object_open_opts,
> I'll remove or shorten it
>
>> + char *btf_custom_path;
>> /* vmlinux BTF override for CO-RE relocations */
>> struct btf *btf_vmlinux_override;
>> /* Lazily initialized kernel module BTFs */
>> @@ -2645,10 +2652,6 @@ static bool obj_needs_vmlinux_btf(const struct bpf_object *obj)
>> struct bpf_program *prog;
>> int i;
>>
>> - /* CO-RE relocations need kernel BTF */
>> - if (obj->btf_ext && obj->btf_ext->core_relo_info.len)
>> - return true;
>> -
>> /* Support for typed ksyms needs kernel BTF */
>> for (i = 0; i < obj->nr_extern; i++) {
>> const struct extern_desc *ext;
>> @@ -2665,6 +2668,13 @@ static bool obj_needs_vmlinux_btf(const struct bpf_object *obj)
>> return true;
>> }
>>
>> + /* CO-RE relocations need kernel BTF, only when btf_custom_path
>> + * is not specified
>> + */
>> + if (obj->btf_ext && obj->btf_ext->core_relo_info.len
>> + && !obj->btf_custom_path)
>> + return true;
>
> not sure why you moved it, I'll move it back to minimize code churn
You're right. 👍
regards,
Shuyi
>
>> +
>> return false;
>> }
>>
>
> [...]
>
next prev parent reply other threads:[~2021-07-17 1:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 12:42 [PATCH bpf-next v4 0/3] Add btf_custom_path in bpf_obj_open_opts Shuyi Cheng
2021-07-13 12:42 ` [PATCH bpf-next v4 1/3] libbpf: Introduce 'btf_custom_path' to 'bpf_obj_open_opts' Shuyi Cheng
2021-07-16 4:51 ` Andrii Nakryiko
2021-07-17 1:15 ` Shuyi Cheng [this message]
2021-07-13 12:42 ` [PATCH bpf-next v4 2/3] libbpf: Fix the possible memory leak on error Shuyi Cheng
2021-07-13 12:42 ` [PATCH bpf-next v4 3/3] selftests/bpf: Switches existing selftests to using open_opts for custom BTF Shuyi Cheng
2021-07-16 4:53 ` Andrii Nakryiko
2021-07-16 20:27 ` Andrii Nakryiko
2021-07-17 1:39 ` Shuyi Cheng
2021-07-16 4:49 ` [PATCH bpf-next v4 0/3] Add btf_custom_path in bpf_obj_open_opts Andrii Nakryiko
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=0fa3b7f1-7928-eff9-1644-df3384171bcd@linux.alibaba.com \
--to=chengshuyi@linux.alibaba.com \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=yhs@fb.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
all inboxes | Powered by JetHome®