From: Stanislav Fomichev <sdf@fomichev.me>
To: Jakub Kicinski <jakub.kicinski@netronome.com>
Cc: Stanislav Fomichev <sdf@google.com>,
netdev@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
quentin.monnet@netronome.com
Subject: Re: [PATCH bpf-next] bpftool: make libbfd optional
Date: Mon, 12 Nov 2018 13:30:59 -0800 [thread overview]
Message-ID: <20181112213059.bkiwxbaymvjjp42b@mini-arch> (raw)
In-Reply-To: <20181112123533.19da3b36@cakuba.netronome.com>
On 11/12, Jakub Kicinski wrote:
> On Mon, 12 Nov 2018 11:58:27 -0800, Stanislav Fomichev wrote:
> > On 11/12, Jakub Kicinski wrote:
> > > On Mon, 12 Nov 2018 10:53:28 -0800, Stanislav Fomichev wrote:
> > > > diff --git a/tools/bpf/bpftool/main.h b/tools/bpf/bpftool/main.h
> > > > index 61d82020af58..ec1bc2ae3c71 100644
> > > > --- a/tools/bpf/bpftool/main.h
> > > > +++ b/tools/bpf/bpftool/main.h
> > > > @@ -147,8 +147,19 @@ int prog_parse_fd(int *argc, char ***argv);
> > > > int map_parse_fd(int *argc, char ***argv);
> > > > int map_parse_fd_and_info(int *argc, char ***argv, void *info, __u32 *info_len);
> > > >
> > > > +#ifdef HAVE_LIBBFD_SUPPORT
> > > > void disasm_print_insn(unsigned char *image, ssize_t len, int opcodes,
> > > > const char *arch, const char *disassembler_options);
> > > > +void disasm_init(void);
> > > > +#else
> > > > +static inline
> > > > +void disasm_print_insn(unsigned char *image, ssize_t len, int opcodes,
> > > > + const char *arch, const char *disassembler_options)
> > > > +{
> > > > + p_err("No libbfd support");
> > > > +}
> > >
> > > I think an error per instruction is a bit much, could we make sure we
> > > error out earlier?
> >
> > I can return int from disasm_print_insn as an indication to
> > stop/continue. Let me know if you have better ideas, will post v2 later
> > today.
>
> Why not simply:
Makes sense. I think I can actually repurpose disasm_init for that (the
function I added to wrap bfd_init, I think I can move the callsite here
without any problems).
> diff --git a/tools/bpf/bpftool/prog.c b/tools/bpf/bpftool/prog.c
> index 5302ee282409..44edf6705ad2 100644
> --- a/tools/bpf/bpftool/prog.c
> +++ b/tools/bpf/bpftool/prog.c
> @@ -466,6 +466,10 @@ static int do_dump(int argc, char **argv)
> int fd;
>
> if (is_prefix(*argv, "jited")) {
> +#ifndef HAVE_LIBBFD_SUPPORT
> + p_err("No libbfd support");
> + return -1;
> +#endif
> member_len = &info.jited_prog_len;
> member_ptr = &info.jited_prog_insns;
> } else if (is_prefix(*argv, "xlated")) {
>
> Perhaps wrapped into some helper in the header to avoid the yuckiness.
prev parent reply other threads:[~2018-11-13 7:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-12 18:53 [PATCH bpf-next] bpftool: make libbfd optional Stanislav Fomichev
2018-11-12 19:42 ` Jakub Kicinski
2018-11-12 19:58 ` Stanislav Fomichev
2018-11-12 20:35 ` Jakub Kicinski
2018-11-12 21:30 ` Stanislav Fomichev [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=20181112213059.bkiwxbaymvjjp42b@mini-arch \
--to=sdf@fomichev.me \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=jakub.kicinski@netronome.com \
--cc=netdev@vger.kernel.org \
--cc=quentin.monnet@netronome.com \
--cc=sdf@google.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