public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: Tao Chen <chentao.kernel@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 KaFai 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>,
	netdev@vger.kernel.org, bpf@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] libbpf: Support raw btf placed in the default path
Date: Mon, 29 Aug 2022 13:48:05 +0800	[thread overview]
Message-ID: <107876eb-4bfe-4d18-607c-08c16271c832@linux.alibaba.com> (raw)
In-Reply-To: <CAEf4BzZPYAZ-ZJXa0CnrpxzFrXjTScfuioF=DOAw4j1L_tMXTg@mail.gmail.com>

Hi Nakryiko, thank you for your reply. Yes, i happed to put the raw
BTF made by myself in /boot on kernel4.19, unluckly it reported error.
So is it possible to allow the raw BTF in /boot directly, athough we
can set the specified btf location again to solve the problem with the
bpf_object_open_opts interface. 


As you say, maybe we can remove the locations[i].raw_btf check, just
use the btf__parse. It looks more concise.


在 2022/8/26 上午4:26, Andrii Nakryiko 写道:
> On Wed, Aug 24, 2022 at 7:05 AM chentao.ct
> <chentao.kernel@linux.alibaba.com> wrote:
>>
>> Now only elf btf can be placed in the default path, raw btf should
>> also can be there.
>>
> 
> It's not clear what you are trying to achieve. Do you want libbpf to
> attempt to load /boot/vmlinux-%1$s as raw BTF as well (so you can sort
> of sneak in pregenerated BTF), or what exactly?
> btf__load_vmlinux_btf() code already supports loading raw BTF, it just
> needs to be explicitly specified in locations table.
> 
> So with your change locations[i].raw_btf check doesn't make sense and
> we need to clean this up.
> 
> But first, let's discuss the use case, instead of your specific solution.
> 
> 
>> Signed-off-by: chentao.ct <chentao.kernel@linux.alibaba.com>
>> ---
>>   tools/lib/bpf/btf.c | 4 ++--
>>   1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/tools/lib/bpf/btf.c b/tools/lib/bpf/btf.c
>> index bb1e06e..b22b5b3 100644
>> --- a/tools/lib/bpf/btf.c
>> +++ b/tools/lib/bpf/btf.c
>> @@ -4661,7 +4661,7 @@ struct btf *btf__load_vmlinux_btf(void)
>>          } locations[] = {
>>                  /* try canonical vmlinux BTF through sysfs first */
>>                  { "/sys/kernel/btf/vmlinux", true /* raw BTF */ },
>> -               /* fall back to trying to find vmlinux ELF on disk otherwise */
>> +               /* fall back to trying to find vmlinux RAW/ELF on disk otherwise */
>>                  { "/boot/vmlinux-%1$s" },
>>                  { "/lib/modules/%1$s/vmlinux-%1$s" },
>>                  { "/lib/modules/%1$s/build/vmlinux" },
>> @@ -4686,7 +4686,7 @@ struct btf *btf__load_vmlinux_btf(void)
>>                  if (locations[i].raw_btf)
>>                          btf = btf__parse_raw(path);
>>                  else
>> -                       btf = btf__parse_elf(path, NULL);
>> +                       btf = btf__parse(path, NULL);
>>                  err = libbpf_get_error(btf);
>>                  pr_debug("loading kernel BTF '%s': %d\n", path, err);
>>                  if (err)
>> --
>> 2.2.1
>>

  reply	other threads:[~2022-08-29  5:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-24 14:05 [PATCH] libbpf: Support raw btf placed in the default path chentao.ct
2022-08-25 20:26 ` Andrii Nakryiko
2022-08-29  5:48   ` Tao Chen [this message]
     [not found]   ` <b9eef4fe-71b3-d15c-6615-282124155508@linux.alibaba.com>
2022-09-09 19:00     ` Andrii Nakryiko
2022-09-12 15:37       ` Tao Chen

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=107876eb-4bfe-4d18-607c-08c16271c832@linux.alibaba.com \
    --to=chentao.kernel@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=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