All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo <arnaldo.melo@gmail.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Andrii Nakryiko <andrii@kernel.org>,
	dwarves@vger.kernel.org, bpf <bpf@vger.kernel.org>,
	Kernel Team <kernel-team@fb.com>, Jiri Olsa <jolsa@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>
Subject: Re: [PATCH dwarves 4/4] btf: add support for split BTF loading and encoding
Date: Wed, 11 Nov 2020 15:34:26 -0300	[thread overview]
Message-ID: <1A8E09AB-8FE7-4B19-9287-663F8B139362@gmail.com> (raw)
In-Reply-To: <CAEf4BzZZ9HcfhVg=YF_0-7tO8Gpp8Jitm1Utg2h_jasXT0n4sw@mail.gmail.com>



On November 11, 2020 3:27:58 PM GMT-03:00, Andrii Nakryiko <andrii.nakryiko@gmail.com> wrote:
>On Wed, Nov 11, 2020 at 3:56 AM Arnaldo Carvalho de Melo
><acme@kernel.org> wrote:
>>
>> Em Thu, Nov 05, 2020 at 09:25:49PM -0800, Andrii Nakryiko escreveu:
>> > Add support for generating split BTF, in which there is a
>designated base
>> > BTF, containing a base set of types, and a split BTF, which extends
>main BTF
>> > with extra types, that can reference types and strings from the
>main BTF.
>>
>> > This is going to be used to generate compact BTFs for kernel
>modules, with
>> > vmlinux BTF being a main BTF, which all kernel modules are based
>off of.
>>
>> > These changes rely on patch set [0] to be present in libbpf
>submodule.
>>
>> >   [0]
>https://patchwork.kernel.org/project/netdevbpf/list/?series=377859&state=*
>>
>> So, applied and added this:
>
>Awesome, thanks! Do you plan to release v1.19 soon?

Yes

>
>>
>> diff --git a/man-pages/pahole.1 b/man-pages/pahole.1
>> index 4b5e0a1bf5462b28..20ee91fc911d4b39 100644
>> --- a/man-pages/pahole.1
>> +++ b/man-pages/pahole.1
>> @@ -185,6 +185,10 @@ Do not encode VARs in BTF.
>>  .B \-\-btf_encode_force
>>  Ignore those symbols found invalid when encoding BTF.
>>
>> +.TP
>> +.B \-\-btf_base
>> +Path to the base BTF file, for instance: vmlinux when encoding
>kernel module BTF information.
>> +
>>  .TP
>>  .B \-l, \-\-show_first_biggest_size_base_type_member
>>  Show first biggest size base_type member.
>>
>> ---------------
>>
>> The entry for btf_encode/-J is missing, I'll add in a followup patch.
>>
>> Also I had to fixup ARGP_btf_base to 321 as I added this, to simplify
>> the kernel scripts and Makefiles:
>>
>>   $ pahole --numeric_version
>>   118
>>   $
>
>Oh, this is nice! Can't really use it with Kbuild now due to backwards
>compatibility, but maybe someday.

Well, if it fails with --numeric_version, then it is old and the warning about the minimal version being v1.19 should be emitted :)

- Arnaldo
>
>>
>> Now to test this all by applying the kernel patches and the encoding
>> module BTF, looking at it, etc.
>>
>> - Arnaldo
>>
>
>[...]

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

  reply	other threads:[~2020-11-11 18:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-06  5:25 [PATCH dwarves 0/4] Add split BTF support to pahole Andrii Nakryiko
2020-11-06  5:25 ` [PATCH dwarves 1/4] btf_encoder: fix array index type numbering Andrii Nakryiko
2020-11-06  5:25 ` [PATCH dwarves 2/4] libbtf: improve variable naming and error reporting when writing out BTF Andrii Nakryiko
2020-11-06  5:25 ` [PATCH dwarves 3/4] libbpf: update libbpf submodlue reference to latest master Andrii Nakryiko
2020-11-06  5:25 ` [PATCH dwarves 4/4] btf: add support for split BTF loading and encoding Andrii Nakryiko
2020-11-11 11:56   ` Arnaldo Carvalho de Melo
2020-11-11 12:19     ` Arnaldo Carvalho de Melo
2020-11-11 18:29       ` Andrii Nakryiko
2020-11-11 18:32         ` Arnaldo
2020-11-13 11:35         ` Arnaldo Carvalho de Melo
2020-11-11 18:27     ` Andrii Nakryiko
2020-11-11 18:34       ` Arnaldo [this message]
2020-11-11 18:50         ` Andrii Nakryiko
2020-11-10 23:34 ` [PATCH dwarves 0/4] Add split BTF support to pahole Andrii Nakryiko
2020-11-11  0:29   ` Arnaldo
2020-11-11  0:35     ` Andrii Nakryiko
2020-11-11  0:38       ` Arnaldo

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=1A8E09AB-8FE7-4B19-9287-663F8B139362@gmail.com \
    --to=arnaldo.melo@gmail.com \
    --cc=acme@kernel.org \
    --cc=andrii.nakryiko@gmail.com \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=dwarves@vger.kernel.org \
    --cc=jolsa@kernel.org \
    --cc=kernel-team@fb.com \
    --cc=namhyung@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.