diff options
| author | He Ying <heying24@huawei.com> | 2021-03-26 06:08:53 -0400 |
|---|---|---|
| committer | Jonathan Corbet <corbet@lwn.net> | 2021-03-31 13:50:59 -0600 |
| commit | f8b427772a0e9bd20cfd9029f7824b39fef44c70 (patch) | |
| tree | 12b93f9166faed42fe9ecc44a912560033d589bc /Documentation/powerpc/papr_hcalls.rst | |
| parent | abb9c078853d0c84f749d272f618a64fb3a27215 (diff) | |
| download | linux-f8b427772a0e9bd20cfd9029f7824b39fef44c70.tar.bz2 | |
docs: powerpc: Fix misspellings and grammar errors
Reported-by: Hulk Robot <hulkci@huawei.com>
Signed-off-by: He Ying <heying24@huawei.com>
Acked-by: Michael Ellerman <mpe@ellerman.id.au>
Link: https://lore.kernel.org/r/20210326100853.173586-1-heying24@huawei.com
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Diffstat (limited to 'Documentation/powerpc/papr_hcalls.rst')
| -rw-r--r-- | Documentation/powerpc/papr_hcalls.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/powerpc/papr_hcalls.rst b/Documentation/powerpc/papr_hcalls.rst index 48fcf1255a33..3d553e8a2937 100644 --- a/Documentation/powerpc/papr_hcalls.rst +++ b/Documentation/powerpc/papr_hcalls.rst @@ -40,7 +40,7 @@ and any in-arguments for the hcall are provided in registers *r4-r12*. If values have to be passed through a memory buffer, the data stored in that buffer should be in Big-endian byte order. -Once control is returns back to the guest after hypervisor has serviced the +Once control returns back to the guest after hypervisor has serviced the 'HVCS' instruction the return value of the hcall is available in *r3* and any out values are returned in registers *r4-r12*. Again like in case of in-arguments, any out values stored in a memory buffer will be in Big-endian byte order. @@ -147,7 +147,7 @@ corresponding opcode values please look into the arch specific header [4]_: | Out: *numBytesRead* | Return Value: *H_Success, H_Parameter, H_P2, H_P3, H_Hardware* -Given a DRC Index of an NVDIMM, read N-bytes from the the metadata area +Given a DRC Index of an NVDIMM, read N-bytes from the metadata area associated with it, at a specified offset and copy it to provided buffer. The metadata area stores configuration information such as label information, bad-blocks etc. The metadata area is located out-of-band of NVDIMM storage |