public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ihor Solodrai <ihor.solodrai@linux.dev>
To: Donglin Peng <dolinux.peng@gmail.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Andrii Nakryiko <andrii@kernel.org>,
	Martin KaFai Lau <martin.lau@linux.dev>,
	Eduard Zingerman <eddyz87@gmail.com>, Song Liu <song@kernel.org>,
	Yonghong Song <yonghong.song@linux.dev>,
	John Fastabend <john.fastabend@gmail.com>,
	KP Singh <kpsingh@kernel.org>,
	Stanislav Fomichev <sdf@fomichev.me>, Hao Luo <haoluo@google.com>,
	Jiri Olsa <jolsa@kernel.org>,
	Nathan Chancellor <nathan@kernel.org>,
	Nicolas Schier <nicolas.schier@linux.dev>,
	Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
	Bill Wendling <morbo@google.com>,
	Justin Stitt <justinstitt@google.com>,
	bpf@vger.kernel.org, dwarves@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
	Alan Maguire <alan.maguire@oracle.com>
Subject: Re: [PATCH bpf-next v1 4/4] resolve_btfids: change in-place update with raw binary output
Date: Wed, 26 Nov 2025 10:32:30 -0800	[thread overview]
Message-ID: <7fb4b953-449d-4f72-8bc7-2becae3cc639@linux.dev> (raw)
In-Reply-To: <CAErzpmvaHxLdooTsHt=YKbz9NDw+LXB8462kRrkzbdp-zJ-=2Q@mail.gmail.com>

On 11/25/25 8:46 PM, Donglin Peng wrote:
> On Wed, Nov 26, 2025 at 9:29 AM Ihor Solodrai <ihor.solodrai@linux.dev> wrote:
>>
>> [...]
>>  static const char * const resolve_btfids_usage[] = {
>> @@ -823,12 +875,13 @@ int main(int argc, const char **argv)
>>                 .funcs    = RB_ROOT,
>>                 .sets     = RB_ROOT,
>>         };
>> +       char out_path[PATH_MAX];
>>         bool fatal_warnings = false;
>>         struct option btfid_options[] = {
>>                 OPT_INCR('v', "verbose", &verbose,
>>                          "be more verbose (show errors, etc)"),
>>                 OPT_STRING(0, "btf", &obj.btf_path, "BTF data",
>> -                          "BTF data"),
>> +                          "input BTF data"),
>>                 OPT_STRING('b', "btf_base", &obj.base_btf_path, "file",
>>                            "path of file providing base BTF"),
>>                 OPT_BOOLEAN(0, "fatal_warnings", &fatal_warnings,
>> @@ -844,6 +897,9 @@ int main(int argc, const char **argv)
>>
>>         obj.path = argv[0];
>>
>> +       if (load_btf(&obj))
>> +               goto out;
> 
> I think I can add the BTF sorting function here based on your patch.

Correct. Any btf2btf transformations will have to happen before the
symbols resolution.

> 
> Thanks,
> Donglin
>> +
>>         if (elf_collect(&obj))
>>                 goto out;
>>
>> @@ -853,23 +909,37 @@ int main(int argc, const char **argv)
>>          */
>>         if (obj.efile.idlist_shndx == -1 ||
>>             obj.efile.symbols_shndx == -1) {
>> -               pr_debug("Cannot find .BTF_ids or symbols sections, nothing to do\n");
>> -               err = 0;
>> -               goto out;
>> +               pr_debug("Cannot find .BTF_ids or symbols sections, skip symbols resolution\n");
>> +               goto dump_btf;
>>         }
>>
>>         if (symbols_collect(&obj))
>>                 goto out;
>>
>> -       if (load_btf(&obj))
>> -               goto out;
>> -
>>         if (symbols_resolve(&obj))
>>                 goto out;
>>
>>         if (symbols_patch(&obj))
>>                 goto out;
>>
>> +       strcpy(out_path, obj.path);
>> +       strcat(out_path, ".btf_ids");
>> +       if (dump_raw_btf_ids(&obj, out_path))
>> +               goto out;
>> +
>> +dump_btf:
>> +       strcpy(out_path, obj.path);
>> +       strcat(out_path, ".btf");
> 
> Do we need to add .btf files to the .gitignore file?

I don't know. Probably?

I take care to cleanup temporary files in the gen-btf.sh, but it makes
sense to .gitignore them anyways, since those are temporary build
artifacts.

> 
> Thanks,
> Donglin
> 
>> +       if (dump_raw_btf(obj.btf, out_path))
>> +               goto out;
>> +
>> +       if (obj.base_btf) {
>> +               strcpy(out_path, obj.path);
>> +               strcat(out_path, ".distilled_base.btf");
>> +               if (dump_raw_btf(obj.base_btf, out_path))
>> +                       goto out;
>> +       }
>> +
>>         if (!(fatal_warnings && warnings))
>>                 err = 0;
>>  out:
>> --
>> 2.52.0
>>


  parent reply	other threads:[~2025-11-26 18:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-26  1:26 [PATCH bpf-next v1 0/4] resolve_btfids: Support for BTF modifications Ihor Solodrai
2025-11-26  1:26 ` [PATCH bpf-next v1 1/4] resolve_btfids: rename object btf field to btf_path Ihor Solodrai
2025-11-26  1:26 ` [PATCH bpf-next v1 2/4] resolve_btfids: factor out load_btf() Ihor Solodrai
2025-11-26  1:26 ` [PATCH bpf-next v1 3/4] resolve_btfids: introduce enum btf_id_kind Ihor Solodrai
2025-11-26  2:09   ` bot+bpf-ci
2025-11-26 19:08     ` Ihor Solodrai
2025-11-26  1:26 ` [PATCH bpf-next v1 4/4] resolve_btfids: change in-place update with raw binary output Ihor Solodrai
2025-11-26  4:46   ` Donglin Peng
2025-11-26 18:22     ` Ihor Solodrai
2025-11-26 18:32     ` Ihor Solodrai [this message]
2025-11-26 13:03   ` Donglin Peng
2025-11-26 19:13     ` Ihor Solodrai
2025-11-26 23:58       ` Ihor Solodrai
2025-11-26 12:36 ` [PATCH bpf-next v1 0/4] resolve_btfids: Support for BTF modifications Alan Maguire
2025-11-26 19:01   ` Ihor Solodrai
2025-12-02 12:56     ` Alan Maguire

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=7fb4b953-449d-4f72-8bc7-2becae3cc639@linux.dev \
    --to=ihor.solodrai@linux.dev \
    --cc=alan.maguire@oracle.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=dolinux.peng@gmail.com \
    --cc=dwarves@vger.kernel.org \
    --cc=eddyz87@gmail.com \
    --cc=haoluo@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=justinstitt@google.com \
    --cc=kpsingh@kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=morbo@google.com \
    --cc=nathan@kernel.org \
    --cc=nick.desaulniers+lkml@gmail.com \
    --cc=nicolas.schier@linux.dev \
    --cc=sdf@fomichev.me \
    --cc=song@kernel.org \
    --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