From: Hari Bathini <hbathini@linux.ibm.com>
To: Sourabh Jain <sourabhjain@linux.ibm.com>, mpe@ellerman.id.au
Cc: mahesh@linux.vnet.ibm.com, linux-doc@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
corbet@lwn.net
Subject: Re: [PATCH v2] powerpc/fadump: sysfs for fadump memory reservation
Date: Thu, 8 Aug 2019 16:47:48 +0530 [thread overview]
Message-ID: <3f2a8648-066e-3639-0328-dd34da759f30@linux.ibm.com> (raw)
In-Reply-To: <20190808100833.30367-1-sourabhjain@linux.ibm.com>
On 08/08/19 3:38 PM, Sourabh Jain wrote:
> Add a sys interface to allow querying the memory reserved by
> fadump for saving the crash dump.
>
> Add an ABI doc entry for new sysfs interface.
> - /sys/kernel/fadump_mem_reserved
>
> Signed-off-by: Sourabh Jain <sourabhjain@linux.ibm.com>
> ---
> v1 -> v2:
> - Added ABI doc for new sysfs interface.
> ---
>
> Documentation/ABI/testing/sysfs-kernel-fadump | 6 ++++++
> Documentation/powerpc/firmware-assisted-dump.rst | 5 +++++
> arch/powerpc/kernel/fadump.c | 14 ++++++++++++++
> 3 files changed, 25 insertions(+)
> create mode 100644 Documentation/ABI/testing/sysfs-kernel-fadump
>
> diff --git a/Documentation/ABI/testing/sysfs-kernel-fadump b/Documentation/ABI/testing/sysfs-kernel-fadump
> new file mode 100644
> index 000000000000..003e2f025dcb
> --- /dev/null
> +++ b/Documentation/ABI/testing/sysfs-kernel-fadump
> @@ -0,0 +1,6 @@
> +What: /sys/kernel/fadump_mem_reserved
> +Date: August 2019
> +Contact: linuxppc-dev@lists.ozlabs.org
> +Description: read only
> + Provide information about the amount of memory
> + reserved by fadump to saving the crash dump.
s/to saving/to save/
Rest looks good..
Thanks
Hari
prev parent reply other threads:[~2019-08-08 11:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-08 10:08 [PATCH v2] powerpc/fadump: sysfs for fadump memory reservation Sourabh Jain
2019-08-08 11:17 ` Hari Bathini [this message]
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=3f2a8648-066e-3639-0328-dd34da759f30@linux.ibm.com \
--to=hbathini@linux.ibm.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@linux.vnet.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=sourabhjain@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).