From: Ross Zwisler <ross.zwisler@linux.intel.com>
To: Dave Jiang <dave.jiang@intel.com>
Cc: dan.j.williams@intel.com, ross.zwisler@linux.intel.com,
linux-acpi@vger.kernel.org, linux-nvdimm@lists.01.org
Subject: Re: [PATCH v3 1/4] acpi: nfit: Add support for detect platform CPU cache flush on power loss
Date: Tue, 30 Jan 2018 17:13:40 -0700 [thread overview]
Message-ID: <20180131001340.GB27220@linux.intel.com> (raw)
In-Reply-To: <151735687346.34477.4956828815153494582.stgit@djiang5-desk3.ch.intel.com>
On Tue, Jan 30, 2018 at 05:01:13PM -0700, Dave Jiang wrote:
> In ACPI 6.2a the platform capability structure has been added to the NFIT
> tables. That provides software the ability to determine whether a system
> supports the auto flushing of CPU caches on power loss. If the capability
> is supported, we do not need to do dax_flush(). Plumbing the path to set the
> property on per region from the NFTI tables.
NFIT
>
> This patch depends on the ACPI NFIT 6.2a platform capabilities support code
> in include/acpi/actbl1.h.
>
> Signed-off-by: Dave Jiang <dave.jiang@intel.com>
Looks good aside from the one nit.
Reviewed-by: Ross Zwisler <ross.zwisler@linux.intel.com>
next prev parent reply other threads:[~2018-01-31 0:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 0:01 [PATCH v3 0/4] add support for platform persistence capabilities Dave Jiang
2018-01-31 0:01 ` [PATCH v3 1/4] acpi: nfit: Add support for detect platform CPU cache flush on power loss Dave Jiang
2018-01-31 0:13 ` Ross Zwisler [this message]
2018-01-31 0:01 ` [PATCH v3 2/4] acpi: nfit: add persistent memory control flag for nd_region Dave Jiang
2018-01-31 0:01 ` [PATCH v3 3/4] libnvdimm: expose platform persistence attribute " Dave Jiang
[not found] ` <151735668391.34477.11820724492631561208.stgit-Cxk7aZI4ujnJARH06PadV2t3HXsI98Cx0E9HWUfgJXw@public.gmane.org>
2018-01-31 0:01 ` [PATCH v3 4/4] nfit-test: Add platform cap support from ACPI 6.2a to test Dave Jiang
2018-01-31 0:15 ` Ross Zwisler
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=20180131001340.GB27220@linux.intel.com \
--to=ross.zwisler@linux.intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=linux-acpi@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 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).