From: WANG Chao <chaowang@redhat.com>
To: 周洲仪 <yizhouzhou@ict.ac.cn>
Cc: zhouzhouyi@gmail.com, kexec@lists.infradead.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
vgoyal@redhat.com
Subject: Re: [PATCH 1/1 v1] the recommended crash memory reservation is too small for x86_64.
Date: Tue, 26 Mar 2013 11:56:26 +0800 [thread overview]
Message-ID: <51511C6A.1000001@redhat.com> (raw)
In-Reply-To: <1cd75ef.b411.13da1646593.Coremail.yizhouzhou@ict.ac.cn>
On 03/25/2013 07:52 PM, 周洲仪 wrote:
> Thanks for reviewing
> Is it sounds good to add following line into section "Boot into System Kernel":
>
> The memory reserved for crash kernel should be no less than the unpacked init ram disk size
> that loaded with dump-capture kernel plus wired memory used by kernel itself.
Sorry, that is just basic knowledge for everyone.
>
> #################
> After all, I have been trapped into "hang after capture" problem when sticking strictly to this document.
> Cheers
> Zhouyi
>
>>
>> On 03/25/2013 06:56 PM, zhouzhouyi@gmail.com wrote:
>> > From: root <root@zzy-Lenovo.(none)>
>> >
>> >
>> > 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.
>>
>> People use different initramfs generators for different purpose. That means
>> the size of initramfs and also its memory consuming can vary very much from
>> each other. You just can't list all these generators and their recommended
>> reserved memory here. Though I have to say crashkernel=128M is good choice.
>>
>> I think it would be better to leave this to user or distribution itself to
>> determine how much memory should be reserved for crash kernel, then export
>> this value to kernel in some ways.
>>
>> Thanks,
>> WANG Chao
>>
>> >
>> >
>> > 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).
>> >
>> > On ppc64, use "crashkernel=128M@32M".
>> >
>> >
>>
>
>
>
>
next prev parent reply other threads:[~2013-03-26 3:56 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 [this message]
2013-03-27 12:28 ` Simon Horman
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=51511C6A.1000001@redhat.com \
--to=chaowang@redhat.com \
--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