public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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@ml01.01.org>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	"rafael.j.wysocki@intel.com" <rafael.j.wysocki@intel.com>
Subject: Re: [PATCH 2/3] acpi, nfit: add dimm device notification support
Date: Mon, 29 Aug 2016 22:19:40 +0000	[thread overview]
Message-ID: <1472509138.1532.61.camel@hpe.com> (raw)
In-Reply-To: <CAPcyv4hdLdGR7LLyHVZsyXK6dNL1+jF927Siqt_D2DfPSifwwA@mail.gmail.com>

On Fri, 2016-08-26 at 11:39 -0700, Dan Williams wrote:
> On Fri, Aug 26, 2016 at 11:26 AM, Kani, Toshimitsu <toshi.kani@hpe.co
> m> wrote:
> > 
> > On Tue, 2016-08-23 at 14:54 -0700, Dan Williams wrote:
> > > 
> > > Per "ACPI 6.1 Section 9.20.3" NVDIMM devices, children of the
> > > ACPI0012 NVDIMM Root device, can receive health event
> > > notifications.
> > > 
> > > Given that these devices are precluded from registering a
> > > notification handler via acpi_driver.acpi_device_ops (due to no
> > > _HID), we use acpi_install_notify_handler() directly.
> > 
> > I've confirmed that this ACPI notify handler is called properly.
> > 
> > > 
> > > The registered handler, acpi_nvdimm_notify(), triggers a poll(2)
> > > event on the nmemX/nfit/flags sysfs attribute when a health event
> > > notification is received.
> > 
> > This sounds good idea, but should we document that the value of
> > sysfs 'flags' itself does not get updated?  User space program will
> > then need to call its _DSM to get health status.
> 
> Yes, this plus the new scrub attribute behavior need documentation.
> I'll prepare a refresh for Documentation/nvdimm/nvdimm.txt.
>
> The need to call a _DSM after a notification event is documented in
> the ACPI spec, but you're right, we do need to connect that language
> to the Linux specific mechanism.

Sounds great.  With that:

Reviewed-by: Toshi Kani <toshi.kani@hpe.com>

Thanks!
-Toshi

  reply	other threads:[~2016-08-29 22:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-23 21:54 [PATCH 0/3] acpi, nfit: nvdimm notification support + tests Dan Williams
2016-08-23 21:54 ` [PATCH 1/3] tools/testing/nvdimm: unit test for acpi_nfit_notify() Dan Williams
2016-08-23 21:54 ` [PATCH 2/3] acpi, nfit: add dimm device notification support Dan Williams
2016-08-26 18:26   ` Kani, Toshimitsu
2016-08-26 18:39     ` Dan Williams
2016-08-29 22:19       ` Kani, Toshimitsu [this message]
2016-09-01 19:46   ` Dan Williams
2016-08-23 21:54 ` [PATCH 3/3] tools/testing/nvdimm: unit test for acpi_nvdimm_notify() Dan Williams
2016-08-23 22:39 ` [PATCH 0/3] acpi, nfit: nvdimm notification support + tests Vishal Verma
2016-08-29 21:50 ` Rafael J. Wysocki

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=1472509138.1532.61.camel@hpe.com \
    --to=toshi.kani@hpe.com \
    --cc=dan.j.williams@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvdimm@ml01.01.org \
    --cc=rafael.j.wysocki@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