linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Keith Busch <keith.busch-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
To: Johannes Thumshirn <jthumshirn-l3A5Bk7waGM@public.gmane.org>
Cc: linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org
Subject: Re: [PATCH 0/3] acpi, nfit: Add dirty shutdown count to sysfs
Date: Thu, 27 Sep 2018 09:21:40 -0600	[thread overview]
Message-ID: <20180927152140.GA19589@localhost.localdomain> (raw)
In-Reply-To: <20180927071135.GB6959-qw2SdCWA0PpjqqEj2zc+bA@public.gmane.org>

On Thu, Sep 27, 2018 at 09:11:35AM +0200, Johannes Thumshirn wrote:
> On Wed, Sep 26, 2018 at 09:24:20PM -0700, Dan Williams wrote:
> > The Intel NVDIMM command specification publishes a dirty-shutdown-count
> > in addition to the dirty-shutdown / flush-failed indication that comes
> > from the ACPI NFIT. This is expected to be a common property of NVDIMMs
> > and is a static hardware health detail to be cached / exported via
> > sysfs.
> > 
> > Add plumbing for retrieving this data at driver load time, publish the
> > count, and use the dynamically retrieved dirty-shutdown indicator to
> > augment the existing 'flush_failed' flag.
> 
> Is this the same thing as the LSS Latch stuff that went into ndctl?

On a related note, the ndctl latch implementation doesn't satisfy all
the needs, so I expect it'll be reverted

  https://lists.01.org/pipermail/linux-nvdimm/2018-September/017892.html

  parent reply	other threads:[~2018-09-27 15:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-27  4:24 [PATCH 0/3] acpi, nfit: Add dirty shutdown count to sysfs Dan Williams
     [not found] ` <153802226065.833068.11943510429252969385.stgit-p8uTFz9XbKj2zm6wflaqv1nYeNYlB/vhral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2018-09-27  4:24   ` [PATCH 1/3] acpi, nfit: Introduce nfit_mem flags Dan Williams
     [not found]     ` <153802226609.833068.13167424056547725578.stgit-p8uTFz9XbKj2zm6wflaqv1nYeNYlB/vhral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2018-09-27 19:37       ` Keith Busch
2018-09-27  4:24   ` [PATCH 2/3] acpi, nfit: Collect shutdown status Dan Williams
     [not found]     ` <153802227150.833068.16202031710309659911.stgit-p8uTFz9XbKj2zm6wflaqv1nYeNYlB/vhral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2018-09-27 19:37       ` Keith Busch
2018-09-27  4:24   ` [PATCH 3/3] tools/testing/nvdimm: Populate dirty shutdown data Dan Williams
     [not found]     ` <153802227683.833068.14067072355792705345.stgit-p8uTFz9XbKj2zm6wflaqv1nYeNYlB/vhral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2018-09-27 19:37       ` Keith Busch
2018-09-27  7:11   ` [PATCH 0/3] acpi, nfit: Add dirty shutdown count to sysfs Johannes Thumshirn
     [not found]     ` <20180927071135.GB6959-qw2SdCWA0PpjqqEj2zc+bA@public.gmane.org>
2018-09-27 15:21       ` Keith Busch [this message]
2018-09-27 15:33       ` Dan Williams

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=20180927152140.GA19589@localhost.localdomain \
    --to=keith.busch-vuqaysv1563yd54fqh9/ca@public.gmane.org \
    --cc=jthumshirn-l3A5Bk7waGM@public.gmane.org \
    --cc=linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.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;
as well as URLs for NNTP newsgroup(s).