From: Daniel Borkmann <daniel@iogearbox.net>
To: Andrii Nakryiko <andriin@fb.com>,
bpf@vger.kernel.org, netdev@vger.kernel.org, ast@fb.com
Cc: andrii.nakryiko@gmail.com, kernel-team@fb.com
Subject: Re: [PATCH bpf-next 0/3] Add generic and raw BTF parsing APIs to libbpf
Date: Mon, 3 Aug 2020 16:45:11 +0200 [thread overview]
Message-ID: <bc4f155d-afe0-9cda-b41b-282e948c15e9@iogearbox.net> (raw)
In-Reply-To: <20200802013219.864880-1-andriin@fb.com>
On 8/2/20 3:32 AM, Andrii Nakryiko wrote:
> It's pretty common for applications to want to parse raw (binary) BTF data
> from file, as opposed to parsing it from ELF sections. It's also pretty common
> for tools to not care whether given file is ELF or raw BTF format. This patch
> series exposes internal raw BTF parsing API and adds generic variant of BTF
> parsing, which will efficiently determine the format of a given fail and will
> parse BTF appropriately.
>
> Patches #2 and #3 removes re-implementations of such APIs from bpftool and
> resolve_btfids tools.
>
> Andrii Nakryiko (3):
> libbpf: add btf__parse_raw() and generic btf__parse() APIs
> tools/bpftool: use libbpf's btf__parse() API for parsing BTF from file
> tools/resolve_btfids: use libbpf's btf__parse() API
>
> tools/bpf/bpftool/btf.c | 54 +------------
> tools/bpf/resolve_btfids/.gitignore | 4 +
> tools/bpf/resolve_btfids/main.c | 58 +-------------
> tools/lib/bpf/btf.c | 114 +++++++++++++++++++---------
> tools/lib/bpf/btf.h | 5 +-
> tools/lib/bpf/libbpf.map | 2 +
> 6 files changed, 89 insertions(+), 148 deletions(-)
> create mode 100644 tools/bpf/resolve_btfids/.gitignore
>
Applied, thanks!
next prev parent reply other threads:[~2020-08-03 14:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-02 1:32 [PATCH bpf-next 0/3] Add generic and raw BTF parsing APIs to libbpf Andrii Nakryiko
2020-08-02 1:32 ` [PATCH bpf-next 1/3] libbpf: add btf__parse_raw() and generic btf__parse() APIs Andrii Nakryiko
2020-08-02 1:32 ` [PATCH bpf-next 2/3] tools/bpftool: use libbpf's btf__parse() API for parsing BTF from file Andrii Nakryiko
2020-08-02 1:32 ` [PATCH bpf-next 3/3] tools/resolve_btfids: use libbpf's btf__parse() API Andrii Nakryiko
2020-08-03 14:45 ` Daniel Borkmann [this message]
2020-08-06 17:39 ` [PATCH bpf-next 0/3] Add generic and raw BTF parsing APIs to libbpf Arnaldo Carvalho de Melo
2020-08-06 17:49 ` Andrii Nakryiko
2020-08-06 18:01 ` Alexei Starovoitov
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=bc4f155d-afe0-9cda-b41b-282e948c15e9@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=andrii.nakryiko@gmail.com \
--cc=andriin@fb.com \
--cc=ast@fb.com \
--cc=bpf@vger.kernel.org \
--cc=kernel-team@fb.com \
--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;
as well as URLs for NNTP newsgroup(s).