[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAE9FiQXEJ-pYpo7rCg+DpYw9hAFTRz97gR1NgRHBheCxdt0+yw@mail.gmail.com>
Date: Thu, 10 Jan 2013 09:11:55 -0800
From: Yinghai Lu <yinghai@...nel.org>
To: Vivek Goyal <vgoyal@...hat.com>
Cc: Thomas Renninger <trenn@...e.de>,
MUNEDA Takahiro <muneda.takahiro@...fujitsu.com>,
Takao Indoh <indou.takao@...fujitsu.com>,
linux-pci@...r.kernel.org, x86@...nel.org,
linux-kernel@...r.kernel.org, andi@...stfloor.org,
tokunaga.keiich@...fujitsu.com, kexec@...ts.infradead.org,
hbabu@...ibm.com, mingo@...hat.com, ddutile@...hat.com,
ishii.hironobu@...fujitsu.com, hpa@...or.com, bhelgaas@...gle.com,
tglx@...utronix.de, khalid@...ehiking.org, horms@...ge.net.au
Subject: Re: [PATCH] Only reset e820 once, even with multiple memmap=exactmap params
On Thu, Jan 10, 2013 at 9:01 AM, Vivek Goyal <vgoyal@...hat.com> wrote:
> On Thu, Jan 10, 2013 at 08:53:18AM -0800, Yinghai Lu wrote:
>> On Thu, Jan 10, 2013 at 6:26 AM, Vivek Goyal <vgoyal@...hat.com> wrote:
>> >
>> > This happens only in case of kdump and not kexec. In case of kdump
>> > we want second kernel to use only selected memory areas.
>> >
>> > In fact this is one improvement area. Instead of using memmap= entries
>> > in kdump case, we should probably modify the e820 map passed in
>> > zero page and get rid of memmap= entries.
>>
>> then how the kdump kernel get saved_max_pfn?
>>
>
> Oh, I forgot about that. May be we can pass saved_max_pfn on command line
> instead of passing all memmap= entries.
then we create another kernel version/kexec tools dependency.
kexec tools need to check kernel version, to see if saved_max_pfn= is supported.
--
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