All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stanislav Fomichev <sdf@google.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>, Hao Luo <haoluo@google.com>,
	Jiri Olsa <jolsa@kernel.org>,
	bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next 0/5] bpftool: Add inline annotations when dumping program CFGs
Date: Fri, 24 Mar 2023 20:05:57 -0700	[thread overview]
Message-ID: <ZB5lFSETgO+HfML+@google.com> (raw)
In-Reply-To: <20230324230209.161008-1-quentin@isovalent.com>

On 03/24, Quentin Monnet wrote:
> This set contains some improvements for bpftool's "visual" program dump
> option, which produces the control flow graph in a DOT format. The main
> objective is to add support for inline annotations on such graphs, so that
> we can have the C source code for the program showing up alongside the
> instructions, when available. The last commits also make it possible to
> display the line numbers or the bare opcodes in the graph, as supported by
> regular program dumps.

> Quentin Monnet (5):
>    bpftool: Fix documentation about line info display for prog dumps
>    bpftool: Fix bug for long instructions in program CFG dumps
>    bpftool: Support inline annotations when dumping the CFG of a program
>    bpftool: Support "opcodes", "linum", "visual" simultaneously
>    bpftool: Support printing opcodes and source file references in CFG

Acked-by: Stanislav Fomichev <sdf@google.com>

Left two small nits. Up to you on whether it's worth to respin or not.

>   .../bpftool/Documentation/bpftool-prog.rst    | 18 ++---
>   tools/bpf/bpftool/bash-completion/bpftool     | 18 +++--
>   tools/bpf/bpftool/btf_dumper.c                | 51 ++++++++++++
>   tools/bpf/bpftool/cfg.c                       | 29 +++----
>   tools/bpf/bpftool/cfg.h                       |  5 +-
>   tools/bpf/bpftool/main.h                      |  2 +
>   tools/bpf/bpftool/prog.c                      | 78 ++++++++++---------
>   tools/bpf/bpftool/xlated_dumper.c             | 52 ++++++++++++-
>   tools/bpf/bpftool/xlated_dumper.h             |  3 +-
>   9 files changed, 184 insertions(+), 72 deletions(-)

> --
> 2.34.1


      parent reply	other threads:[~2023-03-25  3:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-24 23:02 [PATCH bpf-next 0/5] bpftool: Add inline annotations when dumping program CFGs Quentin Monnet
2023-03-24 23:02 ` [PATCH bpf-next 1/5] bpftool: Fix documentation about line info display for prog dumps Quentin Monnet
2023-03-24 23:02 ` [PATCH bpf-next 2/5] bpftool: Fix bug for long instructions in program CFG dumps Quentin Monnet
2023-03-25  2:54   ` Stanislav Fomichev
2023-03-27 10:30     ` Quentin Monnet
2023-03-24 23:02 ` [PATCH bpf-next 3/5] bpftool: Support inline annotations when dumping the CFG of a program Quentin Monnet
2023-03-25  3:05   ` Stanislav Fomichev
2023-03-27 10:30     ` Quentin Monnet
2023-03-24 23:02 ` [PATCH bpf-next 4/5] bpftool: Support "opcodes", "linum", "visual" simultaneously Quentin Monnet
2023-03-24 23:02 ` [PATCH bpf-next 5/5] bpftool: Support printing opcodes and source file references in CFG Quentin Monnet
2023-03-25  3:05 ` 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=ZB5lFSETgO+HfML+@google.com \
    --to=sdf@google.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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.