From: Dan Williams <firstname.lastname@example.org>
To: "Aneesh Kumar K.V" <email@example.com>
Cc: linux-nvdimm <firstname.lastname@example.org>,
Subject: Re: [PATCH v2] libnvdimm: Update persistence domain value for of_pmem and papr_scm device
Date: Mon, 23 Mar 2020 18:21:27 -0700 [thread overview]
Message-ID: <CAPcyv4hfdOUvxDsCrBu05K0pmZ_spCOOiP3YyLLuFWW-HqT+LA@mail.gmail.com> (raw)
On Fri, Mar 20, 2020 at 2:25 AM Aneesh Kumar K.V
> Hi Dan,
> Dan Williams <email@example.com> writes:
> >> Or are you suggesting that application should not infer any of those
> >> details looking at persistence_domain value? If so what is the purpose
> >> of exporting that attribute?
> > The way the patch was worded I thought it was referring to an explicit
> > mechanism outside cpu cache flushes, i.e. a mechanism that required a
> > driver call.
> This patch is blocked because I am not expressing the details correctly.
> I updates this as below. Can you suggest if this is ok? If not what
> alternate wording do you suggest to document "memory controller"
> commit 329b46e88f8cd30eee4776b0de7913ab4d496bd8
> Author: Aneesh Kumar K.V <firstname.lastname@example.org>
> Date: Wed Dec 18 13:53:16 2019 +0530
> libnvdimm: Update persistence domain value for of_pmem and papr_scm device
> Currently, kernel shows the below values
> "cpu_cache" indicates no extra instructions is needed to ensure the persistence
> of data in the pmem media on power failure.
> "memory_controller" indicates cpu cache flush instructions is required to flush
> the data. Platform provides mechanisms to automatically flush outstanding
> write data from memory controler to pmem on system power loss.
> Based on the above use memory_controller for non volatile regions on ppc64.
Looks good to me, want to resend via git-format-patch?
Linux-nvdimm mailing list -- email@example.com
To unsubscribe send an email to firstname.lastname@example.org
prev parent reply other threads:[~2020-03-24 1:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 5:20 [PATCH v2] libnvdimm: Update persistence domain value for of_pmem and papr_scm device Aneesh Kumar K.V
2020-02-09 16:12 ` Dan Williams
2020-02-10 14:20 ` Aneesh Kumar K.V
2020-02-10 18:18 ` Dan Williams
2020-02-11 14:55 ` Aneesh Kumar K.V
2020-02-11 16:38 ` Dan Williams
2020-03-20 9:25 ` Aneesh Kumar K.V
2020-03-24 1:21 ` Dan Williams [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).