From: Taeung Song <treeze.taeung@gmail.com>
To: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
Daniel Borkmann <daniel@iogearbox.net>
Cc: Alexei Starovoitov <ast@kernel.org>,
Martin KaFai Lau <kafai@fb.com>,
netdev@vger.kernel.org, Thomas Girard <thomas.g.girard@free.fr>,
Martin Cermak <mcermak@redhat.com>,
linux-kernel@vger.kernel.org, acme@kernel.org
Subject: Re: pahole + BTF was: Re: [Question] bpf: about a new 'tools/bpf/bpf_dwarf2btf'
Date: Thu, 26 Jul 2018 04:21:31 +0900 [thread overview]
Message-ID: <592c6325-23d0-771b-cc28-6a66842a1265@gmail.com> (raw)
In-Reply-To: <35663517-26e1-c2a2-1554-5dd90be2747f@gmail.com>
On 07/26/2018 03:27 AM, Taeung Song wrote:
> Hi Arnaldo,
>
> On 07/26/2018 02:52 AM, Arnaldo Carvalho de Melo wrote:
>> Em Thu, Jul 26, 2018 at 02:23:32AM +0900, Taeung Song escreveu:
>>> Hi,
>>>
>>> Building bpf programs with .BTF section,
>>> I thought it'd be better to convert dwarf info to .BTF by
>>> a new tool such as 'tools/bpf/bpf_dwarf2btf' instead of pahole
>>> in the future.
>>> Currently for bpf binary that have .BTF section,
>>> we need to use pahole from https://github.com/iamkafai/pahole/tree/btf
>>> with the command line such as "pahole -J bpf_prog.o".
>>> I think it is great but if implementing new 'bpf_dwarf2btf'
>>> (dwarf parsing + btf encoder code written by Martin KaFai Lau on
>>> the pahole project i.e. btf.h, btf_encoder.c, btf_encoder.h,
>>> libbtf.c, libbtf.h),
>>> BPF developers would more easily use functionalities based on BTF.
>>
>> What would be easier exactly? Not having to install a package but build
>> it from the kernel sources?
>>
>> Many kernel developers already have pahole installed for other uses, so
>> no need to install anything.
>>
>
> Understood, but I think there are many non-kernel developers
> developing BPF programs and they mightn't have or use pahole.
>
> So, if providing the 'dwarf2btf' feature on tools/bpf or tools/bpf/bpftool,
> non-kernel developers can also more easily build bpf prog with .BPF, no ?
>
Or, if tools/lib/bpf/ have the 'dwarf2btf' feature,
I think BPF developers can just use bpf programs that have dwarf info
after compiling with clang '-g' and llc '-mattr=dwarfris', even though
not using pahole.
Isn't it good way ?
>> BTW, Daniel, I just pushed to pahole's main repository at:
>>
>> git://git.kernel.org/pub/scm/devel/pahole/pahole.git
>>
>> with the Martin's BTF patch, so no need to pull from the github one,
>> I'll tag v1.12 and announce the release so that distro package
>> maintainers can update their packages.
>>> What do you think about this ? Do you think this is needed ?
>>> Or, already implementing something like this ?
>>> If it is needed, I want to try to make 'tools/bpf/bpf_dwarf2btf'
>>> based on the pahole code. I'd appreciate it, if you reply to this
>>
>> The way Martin took advantage of the work done a long time ago to
>> support CTF out of the same DWARF reading codebase was really cool, not
>> that much work to do, just add a new format to pahole's codebase making
>> it more useful.
>>
>
> I got it !
>
> Thanks,
> Taeung
>
>> I was just so far overly picky with testing it and kept leaving for
>> later to have a good documentation about testing it, vacation and perf
>> maintainership duties kept making this take like forever, grumble :-\
>>
>> - Arnaldo
>>
>
> --
> oh.. :'(
next prev parent reply other threads:[~2018-07-25 19:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-25 17:23 Taeung Song
[not found] ` <20180725175231.GA2121@redhat.com>
2018-07-25 18:27 ` pahole + BTF was: " Taeung Song
2018-07-25 19:06 ` Daniel Borkmann
2018-07-25 19:21 ` Taeung Song [this message]
2018-07-25 20:11 ` Martin KaFai Lau
2018-07-26 0:26 ` Daniel Borkmann
2018-07-26 6:04 ` Taeung Song
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=592c6325-23d0-771b-cc28-6a66842a1265@gmail.com \
--to=treeze.taeung@gmail.com \
--cc=acme@kernel.org \
--cc=arnaldo.melo@gmail.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=kafai@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcermak@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=thomas.g.girard@free.fr \
/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®