openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Andrew Jeffery" <andrew@aj.id.au>
To: "Sui Chen" <suichen6@gmail.com>,
	"OpenBMC Maillist" <openbmc@lists.ozlabs.org>
Subject: Re: [Request for comment] DBus pcap visualizer tool recent updates
Date: Fri, 29 Oct 2021 13:55:14 +1030	[thread overview]
Message-ID: <e0e5e014-cb45-4695-a4db-e4fecfaf29ad@www.fastmail.com> (raw)
In-Reply-To: <CAFaEeaG7ALuM-dLeZ6wYWtgD2oVJyZ1NNVQw+wOv7wmFMw_GQQ@mail.gmail.com>



On Fri, 22 Oct 2021, at 01:30, Sui Chen wrote:
> Hello OpenBMC,
>
> This is about some recent updates to the tool that could be thought of
> as a visual version of Wireshark geared for OpenBMC; it is a desktop
> app that runs on a host, opens a DBus PCAP file that can be obtained
> by `busctl capture` on a BMC, and draws time lines. It draws a time line
> graph, and draws some design ideas from other profiling tools.
>
> The tool has been iterated for a few times and recent small
> improvements include:
>   - Prompts for the user to install dependencies
>   - Ability to display overlapping DBus requests
>   - Ability go group sensor PropertyChanged events together
>
> Intended use cases:
>   - Grab a PCAP on a normally-running BMC and understand what's happening on it.
>   - Grab a PCAP on a BMC with problems and see if it's possible to
> find a problem form the DBus point of view.
>
> Some comments we're looking for include:
>   - Is the UI intuitive?
>   - Does it make understanding the operations of an OpenBMC-based
> system a bit easier?
>   - Does it address your problems when developing for OpenBMC? (It has
> been helpful for us in a few circumstances)
>
> The tool can be found here:
> https://gerrit.openbmc-project.xyz/c/openbmc/openbmc-tools/+/34263

I've merged this now.

Andrew

      reply	other threads:[~2021-10-29  3:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-21 15:00 [Request for comment] DBus pcap visualizer tool recent updates Sui Chen
2021-10-29  3:25 ` Andrew Jeffery [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=e0e5e014-cb45-4695-a4db-e4fecfaf29ad@www.fastmail.com \
    --to=andrew@aj.id.au \
    --cc=openbmc@lists.ozlabs.org \
    --cc=suichen6@gmail.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;
as well as URLs for NNTP newsgroup(s).