Re: [Fastboot] Stupid kexec/kdump question...
From: Vivek Goyal
Date: Wed Sep 27 2006 - 09:12:34 EST
On Wed, Sep 27, 2006 at 08:51:50AM -0400, Valdis.Kletnieks@xxxxxx wrote:
> On Wed, 27 Sep 2006 02:00:07 MDT, Eric W. Biederman said:
> > At that level I would say that below 32M is where you start dealing with
> > custom built programs, instead of slapping a bunch of utilities inside
> > a ramdisk. I suspect with a little care you could get a few K user
> > space executable and fit everything inside of 4M. But I don't know if anyone
> > is that ambitious yet.
> Well, the stripped down kernel is right around 2M. Unfortunately, I need
> to run lvm.static, which is another 1.5M at least. So unless busybox has
> grown support for LVM, I'm looking at 8M at best.
> Another stupid question - I see how the first kernel gets the 'crashkernel='
> parameter and knows how much space there is. But if you set it to 32M@16M,
> how does the kdump kernel know it only has 32M? Or does it just start at
> the 16M line, and it's your job to make sure it doesn't go over the 48M line
> and start corrupting the dump?
Kdump kernel is booted with User defined memory map. For this purpose
kexec-tools passes memmap=exactmap option on command line to the second
kernel. Hence second kernel execution is bounded within reserved memory
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/