From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: Andrii Nakryiko <andrii@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
dwarves@vger.kernel.org, bpf <bpf@vger.kernel.org>,
Kernel Team <kernel-team@fb.com>
Subject: Re: [RFT] Testing 1.22
Date: Thu, 3 Jun 2021 11:57:04 -0300 [thread overview]
Message-ID: <YLjtwB+nGYvcCfgC@kernel.org> (raw)
In-Reply-To: <CAEf4BzYCCWM0WBz0w+vL1rVBjGvLZ7wVtgJCUVr3D-NmVK0MEg@mail.gmail.com>
Em Sat, May 29, 2021 at 05:40:17PM -0700, Andrii Nakryiko escreveu:
> On Fri, May 28, 2021 at 12:45 PM Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com> wrote:
> > commit b579a18a1ea0ee84b90b5302f597dda2edf2f61b
> > Author: Arnaldo Carvalho de Melo <acme@redhat.com>
> > Date: Fri May 28 16:41:30 2021 -0300
> >
> > pahole: Allow encoding BTF into a detached file
> >
> > Previously the newly encoded BTF info was stored into a ELF section in
> > the file where the DWARF info was obtained, but it is useful to just
> > dump it into a separate file, do it.
> >
> > Requested-by: Andrii Nakryiko <andrii@kernel.org>
> > Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
> >
>
> Looks good, see few minor comments below. At some point it probably
> would make sense to formalize "btf_encoder" as a struct with its own
> state instead of passing in multiple variables. It would probably also
Take a look at the tmp.master branch at:
https://git.kernel.org/pub/scm/devel/pahole/pahole.git/log/?h=tmp.master
that btf_elf class isn't used anymore by btf_loader, that uses only
libbpf's APIs, and now we have a btf_encoder class with all the globals,
etc, more baby steps are needed to finally ditch btf_elf altogether and
move on to the parallelization.
I'm doing 'pahole -J vmlinux && btfdiff' after each cset and doing it
very piecemeal as I'm doing will help bisecting any subtle bug this may
introduce.
> allow to parallelize BTF generation, where each CU would proceed in
> parallel generating local BTF, and then the final pass would merge and
> dedup BTFs. Currently reading and processing DWARF is the slowest part
> of the DWARF-to-BTF conversion, parallelization and maybe some other
> optimization seems like the only way to speed the process up.
>
> Acked-by: Andrii Nakryiko <andrii@kernel.org>
Thanks!
- Arnaldo
next prev parent reply other threads:[~2021-06-03 14:57 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 15:20 [RFT] Testing 1.22 Arnaldo Carvalho de Melo
2021-05-27 16:54 ` Andrii Nakryiko
2021-05-27 19:04 ` Arnaldo
2021-05-27 19:14 ` Andrii Nakryiko
2021-05-27 19:55 ` Arnaldo
2021-05-27 20:41 ` Andrii Nakryiko
2021-05-27 21:08 ` Jiri Olsa
2021-05-27 21:57 ` Arnaldo
2021-05-28 19:45 ` Arnaldo Carvalho de Melo
2021-05-29 2:36 ` Andrii Nakryiko
2021-06-01 18:31 ` Arnaldo Carvalho de Melo
2021-06-01 18:32 ` Arnaldo Carvalho de Melo
2021-05-30 0:40 ` Andrii Nakryiko
2021-06-01 18:24 ` Arnaldo Carvalho de Melo
2021-06-03 14:57 ` Arnaldo Carvalho de Melo [this message]
2021-06-05 2:55 ` Andrii Nakryiko
2021-06-07 13:20 ` Parallelizing vmlinux BTF encoding. was " Arnaldo Carvalho de Melo
2021-06-07 15:42 ` Yonghong Song
2021-06-08 0:53 ` Andrii Nakryiko
2021-06-08 12:59 ` Arnaldo Carvalho de Melo
2021-06-15 19:01 ` Arnaldo Carvalho de Melo
2021-06-15 19:13 ` Andrii Nakryiko
2021-06-15 19:38 ` Arnaldo Carvalho de Melo
2021-06-15 20:05 ` Andrii Nakryiko
2021-06-15 20:25 ` Arnaldo Carvalho de Melo
2021-06-15 21:26 ` Andrii Nakryiko
2021-05-30 21:45 ` Jiri Olsa
2021-06-01 19:07 ` Arnaldo Carvalho de Melo
2021-06-02 10:21 ` Michael Petlan
2021-07-15 21:31 ` Michal Suchánek
2021-07-16 13:25 ` Arnaldo Carvalho de Melo
2021-07-16 13:35 ` Luca Boccassi
2021-07-16 19:08 ` Luca Boccassi
[not found] ` <20210716201248.GL24916@kitsune.suse.cz>
2021-07-17 14:35 ` Luca Boccassi
2021-07-17 15:10 ` Michal Suchánek
2021-07-17 15:14 ` Luca Boccassi
2021-07-17 16:36 ` Michal Suchánek
2021-07-17 16:39 ` Luca Boccassi
2021-07-19 10:30 ` Michal Suchánek
2021-07-19 10:34 ` Luca Boccassi
2021-07-19 12:10 ` Luca Boccassi
2021-07-19 21:08 ` Arnaldo Carvalho de Melo
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=YLjtwB+nGYvcCfgC@kernel.org \
--to=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 \
/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;
as well as URLs for NNTP newsgroup(s).