From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "sunfishho12@gmail.com" <sunfishho12@gmail.com>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>
Cc: "Williams, Dan J" <dan.j.williams@intel.com>,
"dave@stgolabs.net" <dave@stgolabs.net>,
"a.manzanares@samsung.com" <a.manzanares@samsung.com>
Subject: Re: [ndctl PATCH 0/2] cxl: Add cxl list image, image-from-file subcommands
Date: Fri, 9 Sep 2022 21:40:53 +0000 [thread overview]
Message-ID: <b26596c33428d6f606c69206c0384d5fc7466a57.camel@intel.com> (raw)
In-Reply-To: <cover.1660895649.git.sunfishho12@gmail.com>
On Fri, 2022-08-19 at 01:50 -0700, sunfishho12@gmail.com wrote:
> From: Matthew Ho <sunfishho12@gmail.com>
>
> cxl list outputs a json array containing the cxl hierarchy, which can be parsed
> to create an image of the cxl topology.
Hi Matthew,
I think this is great, would be nice to have it in the next release. I
have some comments on the patches, but otherwise the general direction
of things seems fine to me.
>
> Patch 1 adds a root port attribute in the cxl list output to switch ports and
> type 3 memory devices to allow determination of which devices hang off of which
> root ports. This preps for patch 2.
>
> Patch 2 adds a subcommand to output the cxl topology, using cxl list options.
> Acceptable output formats include .jpeg, .jpg, and .png. It also adds a
Quick note, I saw the default was 'topology.jpg'. I'm not familiar with
the graphviz libraries, but is it easy to create an SVG file instead?
That is a common format for things like this I imagine, and if it is
possible, it would be nice to have as the default.
> subcommand to output the cxl topology given a text file generated by cxl list.
>
> This pair of patches applies on [1], a pending patch, applied on the tip of the
> create_region branch. The tip at the time of posting is:
>
> commit 8f0433abc2a4 ("cxl/decoder: add a max_available_extent attribute")
>
> [1] https://lore.kernel.org/linux-cxl/20220812221553.92278-1-sunfishho12@gmail.com/
>
> Matthew Ho (2):
> cxl: Add root port attribute to cxl list output
> cxl: Add list image, image-from-file to CXL command
>
> Documentation/cxl/cxl-list.txt | 16 ++
> cxl/filter.c | 279 ++++++++++++++++++++++++++++++++-
> cxl/filter.h | 7 +
> cxl/json.c | 16 +-
> cxl/lib/libcxl.c | 66 ++++++++
> cxl/lib/libcxl.sym | 3 +-
> cxl/libcxl.h | 2 +
> cxl/list.c | 24 +++
> cxl/meson.build | 1 +
> meson.build | 1 +
> 10 files changed, 412 insertions(+), 3 deletions(-)
>
prev parent reply other threads:[~2022-09-09 21:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 8:50 [ndctl PATCH 0/2] cxl: Add cxl list image, image-from-file subcommands sunfishho12
2022-08-19 8:54 ` [ndctl PATCH 1/2] cxl: Add root port attribute to cxl list output sunfishho12
2022-09-09 22:10 ` Verma, Vishal L
2022-08-19 8:57 ` [ndctl PATCH 2/2] cxl: Add list image, image-from-file to CXL command sunfishho12
2022-09-09 22:59 ` Verma, Vishal L
2022-09-09 21:40 ` Verma, Vishal L [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=b26596c33428d6f606c69206c0384d5fc7466a57.camel@intel.com \
--to=vishal.l.verma@intel.com \
--cc=a.manzanares@samsung.com \
--cc=dan.j.williams@intel.com \
--cc=dave@stgolabs.net \
--cc=linux-cxl@vger.kernel.org \
--cc=sunfishho12@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