From: Ira Weiny <ira.weiny@intel.com>
To: Vaibhav Jain <vaibhav@linux.ibm.com>
Cc: Santosh Sivaraj <santosh@fossix.org>,
linux-nvdimm@lists.01.org, linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
Oliver O'Halloran <oohall@gmail.com>,
"Aneesh Kumar K . V" <aneesh.kumar@linux.ibm.com>,
Dan Williams <dan.j.williams@intel.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [RESEND PATCH v9 1/5] powerpc: Document details on H_SCM_HEALTH hcall
Date: Tue, 2 Jun 2020 14:21:23 -0700 [thread overview]
Message-ID: <20200602212122.GB1676657@iweiny-DESK2.sc.intel.com> (raw)
In-Reply-To: <20200602101438.73929-2-vaibhav@linux.ibm.com>
On Tue, Jun 02, 2020 at 03:44:34PM +0530, Vaibhav Jain 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.
>
> 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>
Acked-by: Ira Weiny <ira.weiny@intel.com>
> Signed-off-by: Vaibhav Jain <vaibhav@linux.ibm.com>
> ---
> Changelog:
>
> Resend:
> * None
>
> v8..v9:
> * s/SCM/PMEM device. [ Dan Williams, Aneesh ]
>
> 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 | 46 ++++++++++++++++++++++++---
> 1 file changed, 42 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/powerpc/papr_hcalls.rst b/Documentation/powerpc/papr_hcalls.rst
> index 3493631a60f8..48fcf1255a33 100644
> --- a/Documentation/powerpc/papr_hcalls.rst
> +++ b/Documentation/powerpc/papr_hcalls.rst
> @@ -220,13 +220,51 @@ 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 PMEM device. The asserted bits in the health-bitmap indicate one or more states
> +(described in table below) of the PMEM device 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 | PMEM device is unable to persist memory contents. |
> +| | If the system is powered down, nothing will be saved. |
> ++------+-----------------------------------------------------------------------+
> +| 01 | PMEM device failed to persist memory contents. Either contents were |
> +| | not saved successfully on power down or were not restored properly on |
> +| | power up. |
> ++------+-----------------------------------------------------------------------+
> +| 02 | PMEM device contents are persisted from previous IPL. The data from |
> +| | the last boot were successfully restored. |
> ++------+-----------------------------------------------------------------------+
> +| 03 | PMEM device contents are not persisted from previous IPL. There was no|
> +| | data to restore from the last boot. |
> ++------+-----------------------------------------------------------------------+
> +| 04 | PMEM device memory life remaining is critically low |
> ++------+-----------------------------------------------------------------------+
> +| 05 | PMEM device will be garded off next IPL due to failure |
> ++------+-----------------------------------------------------------------------+
> +| 06 | PMEM device contents cannot persist due to current platform health |
> +| | status. A hardware failure may prevent data from being saved or |
> +| | restored. |
> ++------+-----------------------------------------------------------------------+
> +| 07 | PMEM device is unable to persist memory contents in certain conditions|
> ++------+-----------------------------------------------------------------------+
> +| 08 | PMEM device is encrypted |
> ++------+-----------------------------------------------------------------------+
> +| 09 | PMEM device has successfully completed a requested erase or secure |
> +| | erase procedure. |
> ++------+-----------------------------------------------------------------------+
> +|10:63 | Reserved / Unused |
> ++------+-----------------------------------------------------------------------+
>
> **H_SCM_PERFORMANCE_STATS**
>
> --
> 2.26.2
>
next prev parent reply other threads:[~2020-06-02 21:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 10:14 [RESEND PATCH v9 0/5] powerpc/papr_scm: Add support for reporting nvdimm health Vaibhav Jain
2020-06-02 10:14 ` [RESEND PATCH v9 1/5] powerpc: Document details on H_SCM_HEALTH hcall Vaibhav Jain
2020-06-02 21:21 ` Ira Weiny [this message]
2020-06-02 10:14 ` [RESEND PATCH v9 2/5] seq_buf: Export seq_buf_printf Vaibhav Jain
2020-06-02 10:14 ` [RESEND PATCH v9 3/5] powerpc/papr_scm: Fetch nvdimm health information from PHYP Vaibhav Jain
2020-06-02 18:45 ` Ira Weiny
2020-06-02 10:14 ` [RESEND PATCH v9 4/5] ndctl/papr_scm, uapi: Add support for PAPR nvdimm specific methods Vaibhav Jain
2020-06-02 20:51 ` [RESEND PATCH v9 4/5] ndctl/papr_scm,uapi: " Ira Weiny
2020-06-02 21:05 ` Ira Weiny
2020-06-03 20:28 ` [RESEND PATCH v9 4/5] ndctl/papr_scm, uapi: " Vaibhav Jain
2020-06-03 23:22 ` [RESEND PATCH v9 4/5] ndctl/papr_scm,uapi: " Ira Weiny
2020-06-03 18:11 ` [RESEND PATCH v9 4/5] ndctl/papr_scm, uapi: " Vaibhav Jain
2020-06-03 22:46 ` [RESEND PATCH v9 4/5] ndctl/papr_scm,uapi: " Ira Weiny
2020-06-04 18:42 ` [RESEND PATCH v9 4/5] ndctl/papr_scm, uapi: " Vaibhav Jain
2020-06-04 0:24 ` [RESEND PATCH v9 4/5] ndctl/papr_scm,uapi: " Williams, Dan J
2020-06-04 9:05 ` [RESEND PATCH v9 4/5] ndctl/papr_scm, uapi: " Vaibhav Jain
2020-06-05 0:54 ` [RESEND PATCH v9 4/5] ndctl/papr_scm,uapi: " Williams, Dan J
2020-06-05 15:21 ` [RESEND PATCH v9 4/5] ndctl/papr_scm, uapi: " Vaibhav Jain
2020-06-05 18:19 ` [RESEND PATCH v9 4/5] ndctl/papr_scm,uapi: " Dan Williams
2020-06-02 10:14 ` [RESEND PATCH v9 5/5] powerpc/papr_scm: Implement support for PAPR_PDSM_HEALTH Vaibhav Jain
2020-06-02 21:19 ` Ira Weiny
2020-06-03 19:04 ` Vaibhav Jain
2020-06-03 23:18 ` Ira Weiny
2020-06-04 18:49 ` Vaibhav Jain
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=20200602212122.GB1676657@iweiny-DESK2.sc.intel.com \
--to=ira.weiny@intel.com \
--cc=aneesh.kumar@linux.ibm.com \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=oohall@gmail.com \
--cc=rostedt@goodmis.org \
--cc=santosh@fossix.org \
--cc=vaibhav@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).