All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sui Chen <suichen6@gmail.com>
To: openbmc@lists.ozlabs.org
Subject: [openbmc-tools] dbus-vis: DBus capture visualization tool
Date: Fri, 24 Jul 2020 15:59:27 -0700	[thread overview]
Message-ID: <CAFaEeaE+xp89Q4dc0uS_-mdwy=ngb6-1XqnfdtTZ_1CW-GCE_A@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1471 bytes --]

Hello,

dbus-vis is a GUI tool that does the following:
- It visualizes busctl pcap files, the same format that dbus-pcap reads and
parses.
- It somewhat half-automates the process of doing a capture on the BMC and
transferring back to the host for analysis (console access to the BMC is
required for this purpose.)

dbus-vis started from an IPMI timeline visualization tool that only
processes IPMI requests exposed on DBus. After I learned about dbus-pcap
<https://github.com/openbmc/openbmc-tools/tree/master/amboar/obmc-scripts/dbus-pcap>,
it turns out DBus visualization is a natural extension to this
visualization tool. Because this tool currently accepts the same packet
capture format that dbus-pcap uses (by using a slightly modified version of
dbus-pcap), it kind of functions like a GUI version of dbus-pcap, and is
therefore named "dbus-vis" to indicate what it does.

The main difference between this tool and other existing dbus visualizers
(such as GNU bustle) is that dbus-vis shows data in a compact timeline
format, making it possible to show >10K events simultaneously on the screen
at an acceptable frame rate, as well as making it easier to focus on DBus
performance rather than the dependency of different DBus units (that other
existing tools seem to be focusing on.)

The changes for the first commit of dbus-vis is listed below; any comment
is greatly appreciated.
https://gerrit.openbmc-project.xyz/c/openbmc/openbmc-tools/+/34263

Thanks!
Sui

[-- Attachment #2: Type: text/html, Size: 2359 bytes --]

             reply	other threads:[~2020-07-24 22:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-24 22:59 Sui Chen [this message]
2020-07-25  3:01 ` [openbmc-tools] dbus-vis: DBus capture visualization tool Andrew Jeffery
2020-07-28 13:06   ` Andrew Geissler
2020-08-05 16:55     ` Sui Chen

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='CAFaEeaE+xp89Q4dc0uS_-mdwy=ngb6-1XqnfdtTZ_1CW-GCE_A@mail.gmail.com' \
    --to=suichen6@gmail.com \
    --cc=openbmc@lists.ozlabs.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 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.