From: "Kani, Toshimitsu" <toshi.kani@hpe.com>
To: "dan.j.williams@intel.com" <dan.j.williams@intel.com>,
"dave.jiang@intel.com" <dave.jiang@intel.com>
Cc: "linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: Re: [PATCH v7] ndctl: add list --media-errors support
Date: Thu, 11 May 2017 19:57:14 +0000 [thread overview]
Message-ID: <1494532622.30303.97.camel@hpe.com> (raw)
In-Reply-To: <149453182672.35117.780578492054325470.stgit@djiang5-desk3.ch.intel.com>
On Thu, 2017-05-11 at 12:44 -0700, Dave Jiang wrote:
> ACPI NFIT enabled platforms provide media errors as absolute phyiscal
> address offsets. Add an option to ndctl to display those media errors
> tranlsated to region and namespace device level offsets in an "ndctl
> list" listing. BTT badblocks show is not supported in this iteration
> and will come later.
>
> Signed-off-by: Dave Jiang <dave.jiang@intel.com>
> Reviewed-by: Vishal Verma <vishal.l.verma@intel.com>
> ---
>
> v2: added fix to badblocks display from Toshi's testing result.
> v3: fixed naming issues from Dan's comments.
> fixed badblocks boundary offset calculations from Toshi's
> testing.
> v4: Add indicator to show badblocks exist or not, per Toshi's
> comments.
> v5: Add BTT badblock_count from Toshi and Dan's comments.
> v6: Fix badblock_count to total number of bbs and not range per
> Toshi.
> v7: Fix devices show actual badblocks count instead of region count
> per Toshi.
This works great. :-) Thanks for bearing with me. For the series:
Tested-by: Toshi Kani <toshi.kani@hpe.com>
-Toshi
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
prev parent reply other threads:[~2017-05-11 19:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-11 19:44 [PATCH v7] ndctl: add list --media-errors support Dave Jiang
2017-05-11 19:57 ` Kani, Toshimitsu [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=1494532622.30303.97.camel@hpe.com \
--to=toshi.kani@hpe.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=linux-nvdimm@lists.01.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 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.