Re: [PATCH v8 00/46] x86, mm: map ram from top-down with BRK and memblock.

[Yinghai Lu]

On Wed, Nov 28, 2012 at 12:57 PM, Konrad Rzeszutek Wilk
<konrad.wilk@xxxxxxxxxx> wrote:
> On Wed, Nov 28, 2012 at 11:47:51AM -0800, Yinghai Lu wrote:
>> On Wed, Nov 28, 2012 at 11:35 AM, Konrad Rzeszutek Wilk
>> <konrad.wilk@xxxxxxxxxx> wrote:
>> >
>> > Have done so. I really like how the top-down mechanism works. It is pretty neat!
>> >
>> > Yinghai, I had mostly just comments about the patch descriptions -  I would
>> > appreciate it you could modify the patches to address the little nitpicks I
>> > spotted. And while doing that you can stick
>> > 'Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>' on all patches.
>> >
>> > For the "x86, mm, Xen: Remove mapping_pagetable_reserve()"
>> > you can also put 'Acked-by: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>'
>>
>> Thanks a lot for reviewing. Will update those changelog, and add
>> acked-by and reviewed by...
>>
>> BTW, can you please check my for-x86-boot branch that will allow
>> bzImage to be loaded above 4G on 64bit platform by 64 bit bootloader.
>
> Is there a specific boot loader I should try it out with? I am using
> pxeboot and multiboot right now.

only updated kexec could load high.

but i changed to use early_memmap to copy boot_params and command line
for 64bit.

Not sure if it will break xen.

>
>> Hope it does not break Xen dom0 and domU.
>
> Any specific guest configs? 4G 8G 12G 30G?

8G should be enough.
--
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/