From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "Schofield, Alison" <alison.schofield@intel.com>,
"im, junhyeok" <junhyeok.im@samsung.com>
Cc: "Williams, Dan J" <dan.j.williams@intel.com>,
"bwidawsk@kernel.org" <bwidawsk@kernel.org>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>
Subject: Re: [ndctl 2/3] cxl: add inject-poison command to cxl tool
Date: Wed, 1 Mar 2023 19:01:27 +0000 [thread overview]
Message-ID: <49e6870cbb846beadce4ef475226af0601db63fa.camel@intel.com> (raw)
In-Reply-To: <Y/3MpsTbFfZhTp7C@dell-ArcherCity>
On Tue, 2023-02-28 at 18:43 +0900, Junhyeok Im wrote:
> On Sun, Feb 26, 2023 at 07:21:44PM -0800, Alison Schofield wrote:
>
>
> >
<..>
> > > Also since it is expected no use case of injecting poison into the
> > > same address for multiple devices, this command targets only one
> > > memdev, like write-labels command.
> > >
> > > usage: cxl inject-poison <memdev> -a <dpa> [<options>]
> >
> > maybe -m memdev (to be like others)
>
> AFAIK, memdev is to be specified without "-m" except for 'list' cmd,
> but I think the reason you said is to distinguish memdev from region(e.g."-r").
> (I also found in your previous patch for GET_POISON_LIST that
> memdev and region were separated.)
> If so, codes and documentation should be modified like:
> cxl inject-poison -m <memdev> -a <dpa> [<options>]
Just wanted to chime in on this quickly before having gone through the
rest of the series -
The convention has been if a command can only have one type of
'target', then no need for a -m, or -r etc.
e.g. cxl enable-region region0
But if it can (potentially) have different types of targets, then an
option can be used to determine the target type. e.g. cxl-create-region
was originally intending to allow both memdev and endpoint targets,
hence the -m option to say that the non-option arguments should be
treated as memdevs.
The other place where you'd have options like -m="mem0,mem1" etc is for
filtering or restricting an operation. cxl-list uses the different
options to filter results, but also other commands:
e.g. cxl disable-region --bus=cxl_test all
will disable all regions under cxl_test, but leave alone regions under
another bus.
next prev parent reply other threads:[~2023-03-01 19:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230220045604epcas2p3bc0b1fb688c48ec0b8ae2512adba3513@epcas2p3.samsung.com>
2023-02-20 4:57 ` [ndctl 0/3] Support for inject poison Junhyeok Im
2023-02-20 4:57 ` [ndctl 1/3] libcxl: add memdev inject poison support Junhyeok Im
2023-02-27 2:43 ` Alison Schofield
2023-02-20 4:57 ` [ndctl 2/3] cxl: add inject-poison command to cxl tool Junhyeok Im
2023-02-27 3:21 ` Alison Schofield
2023-02-28 9:43 ` Junhyeok Im
2023-03-01 19:01 ` Verma, Vishal L [this message]
2023-02-27 3:25 ` Alison Schofield
2023-02-28 9:45 ` Junhyeok Im
2023-02-20 4:57 ` [ndctl 3/3] Documentation: add man page documentation for inject-poison Junhyeok Im
2023-02-27 2:38 ` [ndctl 0/3] Support for inject poison Alison Schofield
2023-02-28 9:31 ` Junhyeok Im
2023-05-08 18:39 ` Verma, Vishal L
2023-05-09 9:19 ` Junhyeok Im
[not found] <CGME20230220013613epcas2p23cee8c0fe839f12ca125e97c6f66d815@epcas2p2.samsung.com>
2023-02-20 1:37 ` [ndctl 1/3] libcxl: add memdev inject poison support junhyeok.im
2023-02-20 1:37 ` [ndctl 2/3] cxl: add inject-poison command to cxl tool junhyeok.im
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=49e6870cbb846beadce4ef475226af0601db63fa.camel@intel.com \
--to=vishal.l.verma@intel.com \
--cc=alison.schofield@intel.com \
--cc=bwidawsk@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=junhyeok.im@samsung.com \
--cc=linux-cxl@vger.kernel.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