From: "Niklas Söderlund" <niklas.soderlund@corigine.com>
To: Quentin Monnet <quentin@isovalent.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <kafai@fb.com>, Song Liu <songliubraving@fb.com>,
Yonghong Song <yhs@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@google.com>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>,
bpf@vger.kernel.org, Simon Horman <simon.horman@corigine.com>
Subject: Re: [PATCH bpf-next 0/7] bpftool: Add LLVM as default library for disassembling JIT-ed programs
Date: Sat, 10 Sep 2022 21:41:14 +0200 [thread overview]
Message-ID: <YxzoWn/mbIUD2cTj@oden.dyn.berto.se> (raw)
In-Reply-To: <20220906133613.54928-1-quentin@isovalent.com>
Hi Quentin,
Thanks for your work.
On 2022-09-06 14:36:06 +0100, Quentin Monnet wrote:
> To disassemble instructions for JIT-ed programs, bpftool has relied on the
> libbfd library. This has been problematic in the past: libbfd's interface
> is not meant to be stable and has changed several times, hence the
> detection of the two related features from the Makefile
> (disassembler-four-args and disassembler-init-styled). When it comes to
> shipping bpftool, this has also caused issues with several distribution
> maintainers unwilling to support the feature (for example, Debian's page
> for binutils-dev, libbfd's package, says: "Note that building Debian
> packages which depend on the shared libbfd is Not Allowed.").
>
> This patchset adds support for LLVM as the primary library for
> disassembling instructions for JIT-ed programs.
>
> We keep libbfd as a fallback. One reason for this is that currently it
> works well, we have all we need in terms of features detection in the
> Makefile, so it provides a fallback for disassembling JIT-ed programs if
> libbfd is installed but LLVM is not. The other reason is that libbfd
> supports nfp instruction for Netronome's SmartNICs and can be used to
> disassemble offloaded programs, something that LLVM cannot do (Niklas
> confirmed that the feature is still in use). However, if libbfd's interface
> breaks again in the future, we might reconsider keeping support for it.
I have tested the fallback method for NFP and it works as expected and
one can dump the offloaded program. I know there is discussion about the
output format of the LLVM path, but for the whole series from a NFP
point of view,
Tested-by: Niklas Söderlund <niklas.soderlund@corigine.com>
>
> Quentin Monnet (7):
> bpftool: Define _GNU_SOURCE only once
> bpftool: Remove asserts from JIT disassembler
> bpftool: Split FEATURE_TESTS/FEATURE_DISPLAY definitions in Makefile
> bpftool: Group libbfd defs in Makefile, only pass them if we use
> libbfd
> bpftool: Refactor disassembler for JIT-ed programs
> bpftool: Add LLVM as default library for disassembling JIT-ed programs
> bpftool: Add llvm feature to "bpftool version"
>
> .../bpftool/Documentation/common_options.rst | 8 +-
> tools/bpf/bpftool/Makefile | 65 +++--
> tools/bpf/bpftool/common.c | 2 +
> tools/bpf/bpftool/iter.c | 2 +
> tools/bpf/bpftool/jit_disasm.c | 244 ++++++++++++++----
> tools/bpf/bpftool/main.c | 10 +
> tools/bpf/bpftool/main.h | 29 ++-
> tools/bpf/bpftool/map.c | 1 -
> tools/bpf/bpftool/net.c | 2 +
> tools/bpf/bpftool/perf.c | 2 +
> tools/bpf/bpftool/prog.c | 17 +-
> tools/bpf/bpftool/xlated_dumper.c | 2 +
> 12 files changed, 291 insertions(+), 93 deletions(-)
>
> --
> 2.34.1
>
--
Kind Regards,
Niklas Söderlund
prev parent reply other threads:[~2022-09-10 19:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 13:36 [PATCH bpf-next 0/7] bpftool: Add LLVM as default library for disassembling JIT-ed programs Quentin Monnet
2022-09-06 13:36 ` [PATCH bpf-next 1/7] bpftool: Define _GNU_SOURCE only once Quentin Monnet
2022-09-06 23:14 ` Song Liu
2022-09-06 13:36 ` [PATCH bpf-next 2/7] bpftool: Remove asserts from JIT disassembler Quentin Monnet
2022-09-06 23:16 ` Song Liu
2022-09-06 13:36 ` [PATCH bpf-next 3/7] bpftool: Split FEATURE_TESTS/FEATURE_DISPLAY definitions in Makefile Quentin Monnet
2022-09-06 23:18 ` Song Liu
2022-09-06 13:36 ` [PATCH bpf-next 4/7] bpftool: Group libbfd defs in Makefile, only pass them if we use libbfd Quentin Monnet
2022-09-06 23:31 ` Song Liu
2022-09-07 14:19 ` Quentin Monnet
2022-09-06 13:36 ` [PATCH bpf-next 5/7] bpftool: Refactor disassembler for JIT-ed programs Quentin Monnet
2022-09-06 23:55 ` Song Liu
2022-09-06 13:36 ` [PATCH bpf-next 6/7] bpftool: Add LLVM as default library for disassembling " Quentin Monnet
2022-09-06 23:46 ` Alexei Starovoitov
2022-09-07 14:20 ` Quentin Monnet
2022-09-07 16:10 ` Alexei Starovoitov
2022-09-07 16:33 ` Quentin Monnet
2022-09-07 18:02 ` Yonghong Song
2022-09-11 20:13 ` Quentin Monnet
2022-09-07 0:06 ` Song Liu
2022-09-07 14:20 ` Quentin Monnet
2022-09-07 16:37 ` Song Liu
2022-09-06 13:36 ` [PATCH bpf-next 7/7] bpftool: Add llvm feature to "bpftool version" Quentin Monnet
2022-09-10 19:41 ` Niklas Söderlund [this message]
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=YxzoWn/mbIUD2cTj@oden.dyn.berto.se \
--to=niklas.soderlund@corigine.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=quentin@isovalent.com \
--cc=sdf@google.com \
--cc=simon.horman@corigine.com \
--cc=songliubraving@fb.com \
--cc=yhs@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