public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Yaowei Bai <bywxiaobai@163.com>, corbet@lwn.net
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: add 'crashkernel=auto' entry into kernel-parameters.txt
Date: Sat, 22 Aug 2015 10:57:01 -0700	[thread overview]
Message-ID: <55D8B7ED.90600@infradead.org> (raw)
In-Reply-To: <1440226279-8283-1-git-send-email-bywxiaobai@163.com>

On 08/21/15 23:51, Yaowei Bai wrote:
> There is no 'crashkernel=auto' entry in kernel-parameters.txt, borrow it
> from kexec-kdump-howto.txt file in the kexec-tools-2.0.0 package.
> 
> Signed-off-by: Yaowei Bai <bywxiaobai@163.com>
> ---
>  Documentation/kernel-parameters.txt | 9 +++++++++
>  1 file changed, 9 insertions(+)
> 
> diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
> index 1d6f045..4da77fa 100644
> --- a/Documentation/kernel-parameters.txt
> +++ b/Documentation/kernel-parameters.txt
> @@ -797,6 +797,15 @@ bytes respectively. Such letter suffixes can also be entirely omitted.
>  			It will be ignored when crashkernel=X,high is not used
>  			or memory reserved is below 4G.
>  
> +	crashkernel=auto
> +			This specification allows the kernel to decide how much
> +			meory to reserve for the purposes of kdump. It will make

			memory

> +			this determination based on the amount of memory you have
> +			in your system, and scale the allocation accordingly.
> +			Note that if you have less than 4Gb of memory in your system,
> +			this specification will opt to not allocate any memory for
> +			the purposes of kdump.
> +
>  	cs89x0_dma=	[HW,NET]
>  			Format: <dma>
>  
> 


-- 
~Randy

      reply	other threads:[~2015-08-22 17:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-22  6:51 [PATCH] Documentation: add 'crashkernel=auto' entry into kernel-parameters.txt Yaowei Bai
2015-08-22 17:57 ` Randy Dunlap [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=55D8B7ED.90600@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=bywxiaobai@163.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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