From: Simon Horman <horms@verge.net.au>
To: zhouzhouyi@gmail.com
Cc: yizhouzhou@ict.ac.cn, kexec@lists.infradead.org,
linux-kernel@vger.kernel.org, vgoyal@redhat.com,
linux-doc@vger.kernel.org
Subject: Re: [PATCH 1/1 v1] the recommended crash memory reservation is too small for x86_64.
Date: Wed, 27 Mar 2013 21:28:57 +0900 [thread overview]
Message-ID: <20130327122856.GK17248@verge.net.au> (raw)
In-Reply-To: <1364209009-11592-1-git-send-email-zhouzhouyi@gmail.com>
On Mon, Mar 25, 2013 at 06:56:49PM +0800, zhouzhouyi@gmail.com wrote:
> From: root <root@zzy-Lenovo.(none)>
The above line is bogus.
> On Documentation/kdump/kdump.txt, section Boot into System Kernel: On x86 and x86_64, use
> "crashkernel=64M@16M", but some OSes like ubuntu 12.10 use ram fs larger than 64M, so in these cases the
> memory reserved for crashkernel should be at least 128M.
The above lines are way to wide. Something less than 80 columns is normal.
> Signed-off-by: Zhouyi Zhou <yizhouzhou@ict.ac.cn>
> ---
> Documentation/kdump/kdump.txt | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/kdump/kdump.txt b/Documentation/kdump/kdump.txt
> index 13f1aa0..1e850e0 100644
> --- a/Documentation/kdump/kdump.txt
> +++ b/Documentation/kdump/kdump.txt
> @@ -290,7 +290,9 @@ Boot into System Kernel
> "crashkernel=64M@16M" tells the system kernel to reserve 64 MB of memory
> starting at physical address 0x01000000 (16MB) for the dump-capture kernel.
>
> - On x86 and x86_64, use "crashkernel=64M@16M".
> + On x86 and x86_64, use "crashkernel=64M@16M" (some OSes use init ram fs larger
> +than 64M, for example ubuntu-12.10, use crashkernel=128M@16M instead, or dump-capture
> +kernel will out of memory).
I believe lines of kdmump.txt should also be 80 columns wide or less.
> On ppc64, use "crashkernel=128M@32M".
>
> --
> 1.7.10.4
>
>
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
>
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2013-03-27 12:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 10:56 [PATCH 1/1 v1] the recommended crash memory reservation is too small for x86_64 zhouzhouyi
2013-03-25 11:29 ` WANG Chao
2013-03-25 11:52 ` 周洲仪
2013-03-26 3:56 ` WANG Chao
2013-03-27 12:28 ` Simon Horman [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=20130327122856.GK17248@verge.net.au \
--to=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vgoyal@redhat.com \
--cc=yizhouzhou@ict.ac.cn \
--cc=zhouzhouyi@gmail.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