All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: Sui Chen <suichen6@gmail.com>
Cc: Andrew Jeffery <andrew@aj.id.au>, openbmc@lists.ozlabs.org
Subject: Re: An IPMI Request Visualization Tool
Date: Thu, 21 May 2020 18:39:46 -0400	[thread overview]
Message-ID: <2775.1590100786@dooku> (raw)
In-Reply-To: <CAFaEeaGs0GSiPp9mGVrSMB1brG19ttroPcK-x-p+BN3SnHrU4g@mail.gmail.com>

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


Sui Chen <suichen6@gmail.com> wrote:
    > Thanks for your interest! I'm also using dbus-pcap to track certain
    > issues on the BMC recently, and would like to add support for all DBus
    > messages to the visualization tool, making it somewhat resemble a GUI
    > version of dbus-pcap.  The goal would be to be able to use this tool to
    > investigate both DBus and IPMI. The way I plan to use it would be more
    > similar to how I use GPUView (full-system timeline rather than
    > inspecting individual packets)

Interestingly, I was not that clearly aware of dbus-pcap :-)
I ought to know more, as the lead libpcap maintainer.
Is this visualization tool part of openbmc, or is it a generic dbus
visualization tool?

We recently brought rpcapd into the mix; it can be invoked via ssh.
I wonder if that might help you as a debug tool?

    > If you ask how this user interface might differ from the already
    > existing dbus visualizers such as bustle, my answer would be: it will
    > present information in a way that's more relevant to the BMC, putting a
    > bit more focus on BMC-specific DBus messages, such as HWMon and RedFish
    > DBus messages, to present information in a high signal-noise ratio way.

Would this need to run on the BMC itself?

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2020-05-21 22:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-13 22:38 An IPMI Request Visualization Tool Sui Chen
2020-05-14 13:57 ` Patrick Williams
2020-05-19  1:36   ` Andrew Jeffery
2020-05-21 16:44     ` Sui Chen
2020-05-21 22:39       ` Michael Richardson [this message]
2020-05-26 18:22         ` Brandon Wyman
2020-06-03 12:06         ` Andrew Jeffery
2020-06-08  3:07           ` Michael Richardson
2020-06-11  0:57             ` Andrew Jeffery
2020-05-26 18:56       ` Vijay Khemka

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=2775.1590100786@dooku \
    --to=mcr@sandelman.ca \
    --cc=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 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.