From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Leonard Crestez <leonard.crestez@nxp.com>
Cc: "Georgi Djakov" <georgi.djakov@linaro.org>,
"Bjorn Andersson" <bjorn.andersson@linaro.org>,
"Chanwoo Choi" <cw00.choi@samsung.com>,
"Artur Świgoń" <a.swigon@partner.samsung.com>,
"Evan Green" <evgreen@chromium.org>,
"David Dai" <daidavid1@codeaurora.org>,
"Jordan Crouse" <jcrouse@codeaurora.org>,
"Viresh Kumar" <viresh.kumar@linaro.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH RFC] interconnect: Add interconnect_graph file to debugfs
Date: Thu, 14 Nov 2019 10:41:34 +0800 [thread overview]
Message-ID: <20191114024134.GA47006@kroah.com> (raw)
In-Reply-To: <70f672b39780ba7387d15fd6485f94b75d47b1ec.1573692109.git.leonard.crestez@nxp.com>
On Thu, Nov 14, 2019 at 02:50:49AM +0200, Leonard Crestez wrote:
> The interconnect graphs can be difficult to understand and the current
> "interconnect_summary" file doesn't even display links in any way.
>
> Add a new "interconnect_graph" file to debugfs in the graphviz "dot"
> format which describes interconnect providers, nodes and links.
>
> The file is human-readable and can be visualized by piping through
> graphviz. Example:
>
> ssh $TARGET cat /sys/kernel/debug/interconnect/interconnect_graph \
> | dot -Tsvg > interconnect_graph.svg
You might want to document this somewhere so we don't all have to go dig
it out of the changelog every time we want to look at this file.
>
> Signed-off-by: Leonard Crestez <leonard.crestez@nxp.com>
> ---
> drivers/interconnect/core.c | 66 +++++++++++++++++++++++++++++++++++++
> 1 file changed, 66 insertions(+)
>
> Example output as a github gist:
> https://gist.github.com/cdleonard/2f74a7efe74587e3d4b57cf7983b46a8
>
> The qcs404 driver was hacked to probe on imx, the links to "0" seem to
> from incorrect trailing 0s on DEFINE_QNODE. Possibly fallout from
> switching to ARRAY_SIZE(__VA_ARGS__)?
>
> I'm not sure that "graphviz" is allowed as an output format even in
> debugfs.
Why not! :)
This is great, I love it, nice job, no objection from me.
Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
next prev parent reply other threads:[~2019-11-14 2:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 0:50 [PATCH RFC] interconnect: Add interconnect_graph file to debugfs Leonard Crestez
2019-11-14 2:41 ` Greg Kroah-Hartman [this message]
2019-11-14 17:20 ` Leonard Crestez
2019-11-14 3:49 ` Bjorn Andersson
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=20191114024134.GA47006@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=a.swigon@partner.samsung.com \
--cc=bjorn.andersson@linaro.org \
--cc=cw00.choi@samsung.com \
--cc=daidavid1@codeaurora.org \
--cc=evgreen@chromium.org \
--cc=georgi.djakov@linaro.org \
--cc=jcrouse@codeaurora.org \
--cc=leonard.crestez@nxp.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox