[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1311348392.5772.56.camel@br98xy6r>
Date: Fri, 22 Jul 2011 17:26:32 +0200
From: Michael Holzheu <holzheu@...ux.vnet.ibm.com>
To: Vivek Goyal <vgoyal@...hat.com>
Cc: Martin Schwidefsky <schwidefsky@...ibm.com>, ebiederm@...ssion.com,
hbabu@...ibm.com, mahesh@...ux.vnet.ibm.com,
oomichi@....nes.nec.co.jp, horms@...ge.net.au,
heiko.carstens@...ibm.com, kexec@...ts.infradead.org,
linux-kernel@...r.kernel.org, linux-s390@...r.kernel.org
Subject: Re: [patch 0/9] kdump: Patch series for s390 support
Hello Vivek,
Still thinking how we best get elfcorehdr size...
On Mon, 2011-07-18 at 11:25 -0400, Vivek Goyal wrote:
> On Mon, Jul 18, 2011 at 04:44:13PM +0200, Michael Holzheu wrote:
> You could do that but I think a more generic parameter will make more
> sense.
>
> - Either something along the lines of memmap=
> - Or excludemem=x@y
> - Or modify memory map in s390 specific bootloading protocol block etc.
Wouldn't it be most natural to pass the length along with the address of
the ELF core header? What about extending the kernel elfcorehdr kernel
parameter and adding optional size:
elfcorehdr=<addr>[KMG],<size>[KMG]
Michael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists