From: Dan Williams <dan.j.williams@intel.com> To: Vaibhav Jain <vaibhav@linux.ibm.com> Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>, linux-nvdimm <linux-nvdimm@lists.01.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, "Aneesh Kumar K . V" <aneesh.kumar@linux.ibm.com>, Michael Ellerman <mpe@ellerman.id.au>, Steven Rostedt <rostedt@goodmis.org> Subject: Re: [PATCH v8 1/5] powerpc: Document details on H_SCM_HEALTH hcall Date: Wed, 27 May 2020 11:56:44 -0700 [thread overview] Message-ID: <CAPcyv4jXp1FocSe-fFBA_00TnsjPudrBCuHBfv+zwHA_R0353A@mail.gmail.com> (raw) In-Reply-To: <20200527041244.37821-2-vaibhav@linux.ibm.com> On Tue, May 26, 2020 at 9:13 PM Vaibhav Jain <vaibhav@linux.ibm.com> wrote: > > Add documentation to 'papr_hcalls.rst' describing the bitmap flags > that are returned from H_SCM_HEALTH hcall as per the PAPR-SCM > specification. > Please do a global s/SCM/PMEM/ or s/SCM/NVDIMM/. It's unfortunate that we already have 2 ways to describe persistent memory devices, let's not perpetuate a third so that "grep" has a chance to find interrelated code across architectures. Other than that this looks good to me. > Cc: "Aneesh Kumar K . V" <aneesh.kumar@linux.ibm.com> > Cc: Dan Williams <dan.j.williams@intel.com> > Cc: Michael Ellerman <mpe@ellerman.id.au> > Cc: Ira Weiny <ira.weiny@intel.com> > Signed-off-by: Vaibhav Jain <vaibhav@linux.ibm.com> > --- > Changelog: > v7..v8: > * Added a clarification on bit-ordering of Health Bitmap > > Resend: > * None > > v6..v7: > * None > > v5..v6: > * New patch in the series > --- > Documentation/powerpc/papr_hcalls.rst | 45 ++++++++++++++++++++++++--- > 1 file changed, 41 insertions(+), 4 deletions(-) > > diff --git a/Documentation/powerpc/papr_hcalls.rst b/Documentation/powerpc/papr_hcalls.rst > index 3493631a60f8..45063f305813 100644 > --- a/Documentation/powerpc/papr_hcalls.rst > +++ b/Documentation/powerpc/papr_hcalls.rst > @@ -220,13 +220,50 @@ from the LPAR memory. > **H_SCM_HEALTH** > > | Input: drcIndex > -| Out: *health-bitmap, health-bit-valid-bitmap* > +| Out: *health-bitmap (r4), health-bit-valid-bitmap (r5)* > | Return Value: *H_Success, H_Parameter, H_Hardware* > > Given a DRC Index return the info on predictive failure and overall health of > -the NVDIMM. The asserted bits in the health-bitmap indicate a single predictive > -failure and health-bit-valid-bitmap indicate which bits in health-bitmap are > -valid. > +the NVDIMM. The asserted bits in the health-bitmap indicate one or more states > +(described in table below) of the NVDIMM and health-bit-valid-bitmap indicate > +which bits in health-bitmap are valid. The bits are reported in > +reverse bit ordering for example a value of 0xC400000000000000 > +indicates bits 0, 1, and 5 are valid. > + > +Health Bitmap Flags: > + > ++------+-----------------------------------------------------------------------+ > +| Bit | Definition | > ++======+=======================================================================+ > +| 00 | SCM device is unable to persist memory contents. | > +| | If the system is powered down, nothing will be saved. | > ++------+-----------------------------------------------------------------------+ > +| 01 | SCM device failed to persist memory contents. Either contents were not| > +| | saved successfully on power down or were not restored properly on | > +| | power up. | > ++------+-----------------------------------------------------------------------+ > +| 02 | SCM device contents are persisted from previous IPL. The data from | > +| | the last boot were successfully restored. | > ++------+-----------------------------------------------------------------------+ > +| 03 | SCM device contents are not persisted from previous IPL. There was no | > +| | data to restore from the last boot. | > ++------+-----------------------------------------------------------------------+ > +| 04 | SCM device memory life remaining is critically low | > ++------+-----------------------------------------------------------------------+ > +| 05 | SCM device will be garded off next IPL due to failure | > ++------+-----------------------------------------------------------------------+ > +| 06 | SCM contents cannot persist due to current platform health status. A | > +| | hardware failure may prevent data from being saved or restored. | > ++------+-----------------------------------------------------------------------+ > +| 07 | SCM device is unable to persist memory contents in certain conditions | > ++------+-----------------------------------------------------------------------+ > +| 08 | SCM device is encrypted | > ++------+-----------------------------------------------------------------------+ > +| 09 | SCM device has successfully completed a requested erase or secure | > +| | erase procedure. | > ++------+-----------------------------------------------------------------------+ > +|10:63 | Reserved / Unused | > ++------+-----------------------------------------------------------------------+ > > **H_SCM_PERFORMANCE_STATS** > > -- > 2.26.2 > _______________________________________________ Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org To unsubscribe send an email to linux-nvdimm-leave@lists.01.org
next prev parent reply other threads:[~2020-05-27 18:56 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-27 4:12 [PATCH v8 0/5] powerpc/papr_scm: Add support for reporting nvdimm health Vaibhav Jain 2020-05-27 4:12 ` [PATCH v8 1/5] powerpc: Document details on H_SCM_HEALTH hcall Vaibhav Jain 2020-05-27 18:56 ` Dan Williams [this message] 2020-05-28 19:24 ` Vaibhav Jain 2020-05-27 4:12 ` [PATCH v8 2/5] seq_buf: Export seq_buf_printf Vaibhav Jain 2020-06-01 12:01 ` Vaibhav Jain 2020-06-01 13:48 ` Steven Rostedt 2020-06-01 14:46 ` Vaibhav Jain 2020-05-27 4:12 ` [PATCH v8 3/5] powerpc/papr_scm: Fetch nvdimm health information from PHYP Vaibhav Jain 2020-05-27 9:54 ` Aneesh Kumar K.V 2020-05-27 4:12 ` [PATCH v8 4/5] ndctl/papr_scm,uapi: Add support for PAPR nvdimm specific methods Vaibhav Jain 2020-05-27 9:55 ` Aneesh Kumar K.V 2020-05-27 4:12 ` [PATCH v8 5/5] powerpc/papr_scm: Implement support for PAPR_SCM_PDSM_HEALTH Vaibhav Jain 2020-05-27 9:55 ` Aneesh Kumar K.V
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=CAPcyv4jXp1FocSe-fFBA_00TnsjPudrBCuHBfv+zwHA_R0353A@mail.gmail.com \ --to=dan.j.williams@intel.com \ --cc=aneesh.kumar@linux.ibm.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-nvdimm@lists.01.org \ --cc=linuxppc-dev@lists.ozlabs.org \ --cc=mpe@ellerman.id.au \ --cc=rostedt@goodmis.org \ --cc=vaibhav@linux.ibm.com \ --subject='Re: [PATCH v8 1/5] powerpc: Document details on H_SCM_HEALTH hcall' \ /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
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).