From: "Kani, Toshimitsu" <toshi.kani@hpe.com>
To: "dan.j.williams@intel.com" <dan.j.williams@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: Re: [PATCH] libnvdimm, pmem: Add sysfs notifications to badblocks
Date: Mon, 12 Jun 2017 20:18:33 +0000 [thread overview]
Message-ID: <1497298683.9288.14.camel@hpe.com> (raw)
In-Reply-To: <20170612164206.5794-1-toshi.kani@hpe.com>
On Mon, 2017-06-12 at 10:42 -0600, Toshi Kani wrote:
> Sysfs "badblocks" information may be updated during run-time via
> MCE, SCI, and sysfs "scrub".
>
> Add support to send sysfs notifications to sysfs "badblocks" file
> under region and pmem directories when their badblocks information
> is re-evaluated (but is not necessarily changed) during run-time.
Thinking further, this notification should be sent when a badblock is
cleared via _DSM. I will update and send v2.
-Toshi
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
WARNING: multiple messages have this Message-ID (diff)
From: "Kani, Toshimitsu" <toshi.kani@hpe.com>
To: "dan.j.williams@intel.com" <dan.j.williams@intel.com>
Cc: "Knippers, Linda" <linda.knippers@hpe.com>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"vishal.l.verma@intel.com" <vishal.l.verma@intel.com>
Subject: Re: [PATCH] libnvdimm, pmem: Add sysfs notifications to badblocks
Date: Mon, 12 Jun 2017 20:18:33 +0000 [thread overview]
Message-ID: <1497298683.9288.14.camel@hpe.com> (raw)
In-Reply-To: <20170612164206.5794-1-toshi.kani@hpe.com>
On Mon, 2017-06-12 at 10:42 -0600, Toshi Kani wrote:
> Sysfs "badblocks" information may be updated during run-time via
> MCE, SCI, and sysfs "scrub".
>
> Add support to send sysfs notifications to sysfs "badblocks" file
> under region and pmem directories when their badblocks information
> is re-evaluated (but is not necessarily changed) during run-time.
Thinking further, this notification should be sent when a badblock is
cleared via _DSM. I will update and send v2.
-Toshi
next prev parent reply other threads:[~2017-06-12 20:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-12 16:42 [PATCH] libnvdimm, pmem: Add sysfs notifications to badblocks Toshi Kani
2017-06-12 16:42 ` Toshi Kani
2017-06-12 20:18 ` Kani, Toshimitsu [this message]
2017-06-12 20:18 ` Kani, Toshimitsu
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=1497298683.9288.14.camel@hpe.com \
--to=toshi.kani@hpe.com \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--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.