From: WANG Cong <xiyou.wangcong@gmail.com>
To: kexec@lists.infradead.org
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH -next] Documentation: Improve crashkernel= description
Date: Mon, 7 Feb 2011 10:59:40 +0000 (UTC) [thread overview]
Message-ID: <iiojar$cvf$1@dough.gmane.org> (raw)
In-Reply-To: 4D4F5810.3070300@parallels.com
On Sun, 06 Feb 2011 20:25:20 -0600, Rob Landley wrote:
>
> Suitable offset as in parses a known image type (ELF, bzImage, etc) to
> find the start address? Or just assumes the entry point and load
> address are the same?
No, that is the start physical address of crashkernel, which should be
your system RAM not reserved by your BIOS etc..
The beginning of the physical memory is often fragmented, thus specifying
a fixed offset may not work on a specific machine.
>
> Is this the size for just the kernel image, or also for the physical
> memory it uses so it won't overwrite the existing kernel's stuff on the
> way up? (If a compressed kernel wants to decompress itself or extract
> an initramfs for itself, what happens?)
>
The size means the whole physical memory size available to the second
kernel (i.e. crash kernel), which includes the memory occupied by
vmlinuz, initrd, *and* the memory which will be used by the programs
inside initrd (e.g. /sbin/init). If this memory is not sufficient,
you will get OOM.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2011-02-07 11:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-06 15:41 [PATCH -next] Documentation: Improve crashkernel= description Ahmed S. Darwish
2011-02-06 15:41 ` Ahmed S. Darwish
2011-02-06 21:57 ` Simon Horman
2011-02-06 21:57 ` Simon Horman
2011-02-07 2:25 ` Rob Landley
2011-02-07 2:25 ` Rob Landley
2011-02-07 2:35 ` Eric W. Biederman
2011-02-07 2:35 ` Eric W. Biederman
2011-02-07 2:42 ` Simon Horman
2011-02-07 2:42 ` Simon Horman
2011-02-07 14:33 ` Vivek Goyal
2011-02-07 14:33 ` Vivek Goyal
2011-02-07 10:59 ` WANG Cong [this message]
2011-02-07 4:14 ` Randy Dunlap
2011-02-07 4:14 ` Randy Dunlap
2011-02-07 11:30 ` [PATCH v2 " Ahmed S. Darwish
2011-02-07 11:30 ` Ahmed S. Darwish
2011-02-07 11:41 ` Simon Horman
2011-02-07 11:41 ` Simon Horman
2011-02-07 14:25 ` Vivek Goyal
2011-02-07 14:25 ` Vivek Goyal
2011-02-07 16:01 ` [PATCH v3 " Ahmed S. Darwish
2011-02-07 16:01 ` Ahmed S. Darwish
2011-02-08 18:50 ` Randy Dunlap
2011-02-08 18:50 ` Randy Dunlap
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='iiojar$cvf$1@dough.gmane.org' \
--to=xiyou.wangcong@gmail.com \
--cc=kexec@lists.infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.