Netdev List
 help / color / mirror / Atom feed
From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: alexei.starovoitov@gmail.com, daniel@iogearbox.net
Cc: netdev@vger.kernel.org, oss-drivers@netronome.com,
	Jakub Kicinski <jakub.kicinski@netronome.com>
Subject: [PATCH bpf-next 0/8] tools: bpftool: visualization support for eBPF program
Date: Mon, 26 Feb 2018 20:12:46 -0800	[thread overview]
Message-ID: <20180227041254.32442-1-jakub.kicinski@netronome.com> (raw)

Jiong says:

This patch set is an application of CFG information on eBPF program
visualization. It presents some initial code for building CFG information
from eBPF instruction sequences.

After we get eBPF program bytecode, we do sub-program detection and
basic-block partition. These information then are visualized into DOT
graph.

The user could use any DOT graphic tools (xdot, graphviz etc) to view it.

For example:

  bpftool prog dump xlated id 2 visual &>output.dot

  [xdot | dotty] output.dot
    dot -Tpng -o output.png

This initial patch set hasn't tuned much on the dot description layout
nor decoration, we could improve them later once the direction of the patch
set is agreed on. We could also visualize some static analysis performance
data.


Jiong Wang (7):
  tools: bpftool: remove unnecessary 'if' to reduce indentation
  tools: bpftool: factor out xlated dump related code into separate file
  tools: bpftool: detect sub-programs from the eBPF sequence
  tools: bpftool: partition basic-block for each function in the CFG
  tools: bpftool: add out edges for each basic-block
  tools: bpftool: generate .dot graph from CFG information
  tools: bpftool: new command-line option and documentation for 'visual'

Quentin Monnet (1):
  tools: bpftool: add bash completion for CFG dump

 tools/bpf/bpftool/Documentation/bpftool-prog.rst |  18 +-
 tools/bpf/bpftool/bash-completion/bpftool        |  13 +-
 tools/bpf/bpftool/cfg.c                          | 510 +++++++++++++++++++++++
 tools/bpf/bpftool/cfg.h                          |  39 ++
 tools/bpf/bpftool/prog.c                         | 305 ++------------
 tools/bpf/bpftool/xlated_dumper.c                | 334 +++++++++++++++
 tools/bpf/bpftool/xlated_dumper.h                |  60 +++
 7 files changed, 994 insertions(+), 285 deletions(-)
 create mode 100644 tools/bpf/bpftool/cfg.c
 create mode 100644 tools/bpf/bpftool/cfg.h
 create mode 100644 tools/bpf/bpftool/xlated_dumper.c
 create mode 100644 tools/bpf/bpftool/xlated_dumper.h

-- 
2.15.1

             reply	other threads:[~2018-02-27  4:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-27  4:12 Jakub Kicinski [this message]
2018-02-27  4:12 ` [PATCH bpf-next 1/8] tools: bpftool: remove unnecessary 'if' to reduce indentation Jakub Kicinski
2018-02-27  4:12 ` [PATCH bpf-next 2/8] tools: bpftool: factor out xlated dump related code into separate file Jakub Kicinski
2018-02-27  4:12 ` [PATCH bpf-next 3/8] tools: bpftool: detect sub-programs from the eBPF sequence Jakub Kicinski
2018-02-27  4:25   ` Alexei Starovoitov
2018-02-27  4:12 ` [PATCH bpf-next 4/8] tools: bpftool: partition basic-block for each function in the CFG Jakub Kicinski
2018-02-27  4:12 ` [PATCH bpf-next 5/8] tools: bpftool: add out edges for each basic-block Jakub Kicinski
2018-02-27  4:12 ` [PATCH bpf-next 6/8] tools: bpftool: generate .dot graph from CFG information Jakub Kicinski
2018-02-27  4:12 ` [PATCH bpf-next 7/8] tools: bpftool: new command-line option and documentation for 'visual' Jakub Kicinski
2018-02-27  4:12 ` [PATCH bpf-next 8/8] tools: bpftool: add bash completion for CFG dump Jakub Kicinski

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=20180227041254.32442-1-jakub.kicinski@netronome.com \
    --to=jakub.kicinski@netronome.com \
    --cc=alexei.starovoitov@gmail.com \
    --cc=daniel@iogearbox.net \
    --cc=netdev@vger.kernel.org \
    --cc=oss-drivers@netronome.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