From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Alison Schofield <alison.schofield@intel.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Dave Jiang <dave.jiang@intel.com>,
Ben Widawsky <bwidawsk@kernel.org>, <nvdimm@lists.linux.dev>,
<linux-cxl@vger.kernel.org>
Subject: Re: [ndctl PATCH 4/5] cxl/list: add --media-errors option to cxl list
Date: Mon, 21 Nov 2022 10:57:11 +0000 [thread overview]
Message-ID: <20221121105711.0000770c@Huawei.com> (raw)
In-Reply-To: <Y3bG884BuHoGnbuE@aschofie-mobl2>
On Thu, 17 Nov 2022 15:42:43 -0800
Alison Schofield <alison.schofield@intel.com> wrote:
> On Wed, Nov 16, 2022 at 01:03:45PM +0000, Jonathan Cameron wrote:
> > On Thu, 10 Nov 2022 19:20:07 -0800
> > alison.schofield@intel.com wrote:
> >
> > > From: Alison Schofield <alison.schofield@intel.com>
> > >
> > > The --media-errors option to 'cxl list' retrieves poison lists
> > > from memory devices (supporting the capability) and displays
> > > the returned media-error records in the cxl list json. This
> > > option can apply to memdevs or regions.
> > >
> > > Signed-off-by: Alison Schofield <alison.schofield@intel.com>
> > > ---
> > > Documentation/cxl/cxl-list.txt | 64 ++++++++++++++++++++++++++++++++++
> > > cxl/filter.c | 2 ++
> > > cxl/filter.h | 1 +
> > > cxl/list.c | 2 ++
> > > 4 files changed, 69 insertions(+)
> > >
> > > diff --git a/Documentation/cxl/cxl-list.txt b/Documentation/cxl/cxl-list.txt
> > > index 14a2b4bb5c2a..24a0cf97cef2 100644
> > > --- a/Documentation/cxl/cxl-list.txt
> > > +++ b/Documentation/cxl/cxl-list.txt
> > > @@ -344,6 +344,70 @@ OPTIONS
> > > --region::
> > > Specify CXL region device name(s), or device id(s), to filter the listing.
> > >
> > > +-a::
> > > +--media-errors::
> > > + Include media-error information. The poison list is retrieved
> > > + from the device(s) and media error records are added to the
> > > + listing. This option applies to memdevs and regions where
> > > + devices support the poison list capability.
> >
> > I'm not sure media errors is a good name. The poison doesn't have to originate
> > in the device. Given we are logging poison with "external" as the source
> > those definitely don't come from the device and may have nothing to do
> > with 'media' as such.
> >
> > Why not just call it poison?
> >
> --media-errors probably originated from ndctl tool which used
> that same option name, but it fits in with the CXL Spec language.
>
> The CXL Spec calls the records returned from the 'Get Poison List'
> command Media Error Records. It refers to poison as media errors.
> So, here, in a command that lists things - the thing(s) being listed
> is(are) 'media error record(s)'.
>
> I see what you're saying about 'External' source. Does that mean
> an 'External' source caused an actual media error?
Hmm. I suspect this all evolved. An External source need not have
anything to do with media (could be corruption in some random cache
or on interconnect or even that a link collapsed potentially).
Ah well, I'm fine with any naming you prefer. No idea if the NVDIMM
equivalent has a the same issue with externally generated poison.
>
> So, that 'Why not poison?' answer. I'm easily swayed either way.
> Would you suggest:
> > > +
> > > +----
> > > +# cxl list -m mem11 --media-errors
>
> cxl list -m mem1 --poison
>
> > > + "media_errors":{
> > > + "nr_media_errors":1,
> > > + "media_error_records":[
>
> and rename the fields above:
> "poison_errors"
> "nr_poison_errors"
> "poison_error_records"
>
>
That works for me, but if it's going to confuse people familiar with
other similar cases, then I don't mind the original naming that much.
Jonathan
next prev parent reply other threads:[~2022-11-21 10:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 3:20 [ndctl PATCH 0/3] Support poison list retrieval alison.schofield
2022-11-11 3:20 ` [ndctl PATCH 1/5] libcxl: add interfaces for GET_POISON_LIST mailbox commands alison.schofield
2022-11-16 12:56 ` Jonathan Cameron
2022-11-17 23:45 ` Alison Schofield
2022-11-11 3:20 ` [ndctl PATCH 2/5] cxl: add an optional pid check to event parsing alison.schofield
2022-11-16 12:57 ` Jonathan Cameron
2022-11-11 3:20 ` [ndctl PATCH 3/5] cxl/list: collect and parse the poison list records alison.schofield
2022-11-11 3:20 ` [ndctl PATCH 4/5] cxl/list: add --media-errors option to cxl list alison.schofield
2022-11-16 13:03 ` Jonathan Cameron
2022-11-17 23:42 ` Alison Schofield
2022-11-21 10:57 ` Jonathan Cameron [this message]
2022-11-11 3:20 ` [ndctl PATCH 5/5] test: add a cxl-get-poison test alison.schofield
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=20221121105711.0000770c@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=alison.schofield@intel.com \
--cc=bwidawsk@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=vishal.l.verma@intel.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