From: Taeung Song <treeze.taeung@gmail.com>
To: Daniel Borkmann <daniel@iogearbox.net>,
Alexei Starovoitov <ast@kernel.org>,
Martin KaFai Lau <kafai@fb.com>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [Question] bpf: about a new 'tools/bpf/bpf_dwarf2btf'
Date: Thu, 26 Jul 2018 02:23:32 +0900 [thread overview]
Message-ID: <47cfb90e-a9f4-8127-2b89-0e20d9fda2f0@gmail.com> (raw)
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 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
Thanks,
Taeung
next reply other threads:[~2018-07-25 17:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-25 17:23 Taeung Song [this message]
[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
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=47cfb90e-a9f4-8127-2b89-0e20d9fda2f0@gmail.com \
--to=treeze.taeung@gmail.com \
--cc=acme@redhat.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=kafai@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.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 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®