Thanks for looking into this patch Mpe, Michael Ellerman <[email protected]> writes:
> Vaibhav Jain <[email protected]> writes: > >> 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: Dan Williams <[email protected]> >> Cc: Michael Ellerman <[email protected]> >> Cc: "Aneesh Kumar K . V" <[email protected]> >> Signed-off-by: Vaibhav Jain <[email protected]> >> --- >> Changelog: >> >> v5..v6 >> * New patch in the series >> --- >> Documentation/powerpc/papr_hcalls.rst | 43 ++++++++++++++++++++++++--- >> 1 file changed, 39 insertions(+), 4 deletions(-) >> >> diff --git a/Documentation/powerpc/papr_hcalls.rst >> b/Documentation/powerpc/papr_hcalls.rst >> index 3493631a60f8..9a5ba5eaf323 100644 >> --- a/Documentation/powerpc/papr_hcalls.rst >> +++ b/Documentation/powerpc/papr_hcalls.rst >> @@ -220,13 +220,48 @@ 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. >> + >> +Health Bitmap Flags: >> + >> ++------+-----------------------------------------------------------------------+ >> +| Bit | Definition >> | >> ++======+=======================================================================+ >> +| 00 | SCM device is unable to persist memory contents. >> | >> +| | If the system is powered down, nothing will be saved. >> | >> ++------+-----------------------------------------------------------------------+ > > Are these correct bit numbers or backward IBM big endian bit numbers? > > ie. which bit is LSB? These bit numbers index to a 64-bit dword laid in IBM big endian format. So LSB would be at the located at a higher address. For example 0xC400000000000000 indicates bits 0, 1, and 5 are valid. > > cheers > _______________________________________________ > Linux-nvdimm mailing list -- [email protected] > To unsubscribe send an email to [email protected] _______________________________________________ Linux-nvdimm mailing list -- [email protected] To unsubscribe send an email to [email protected]
