Re: [patch] tip/x86_64: fix e820 merge issue which broke max_pfn_mapped

From: Yinghai Lu
Date: Tue Jul 08 2008 - 20:48:16 EST


On Tue, Jul 8, 2008 at 4:08 PM, Suresh Siddha <suresh.b.siddha@xxxxxxxxx> wrote:
> With out this 64bit tip/master doesn't boot using ACPI on my system.
> ---
>
> max_pfn_mapped should include all e820 entries.
> The direct mapping extends to max_pfn_mapped, so that we can directly access
> apertures, ACPI and other tables without having to play with fixmaps.
>
> With this, my system with 1GB memory boots fine with ACPI enabled.
>
> Signed-off-by: Suresh Siddha <suresh.b.siddha@xxxxxxxxx>
> ---

please check

[PATCH] x86: introduce page_size_mask for 64bit
http://lkml.org/lkml/2008/7/8/49
[PATCH] x86: not overmap than end in init_memory_mapping - 64bit
http://lkml.org/lkml/2008/7/8/50

with this patch, on system that support gbpages
change
last_map_addr: 1080000000 end: 1078000000
to
last_map_addr: 1078000000 end: 1078000000

/sys/kernel/debug/kernel_page_tables
0xffff881040000000-0xffff881074400000 836M RW PSE GLB NX pmd
0xffff881074400000-0xffff8810744b0000 704K RW GLB NX pte
0xffff8810744b0000-0xffff8810744c0000 64K RW PCD GLB NX pte
0xffff8810744c0000-0xffff881074600000 1280K RW GLB NX pte
0xffff881074600000-0xffff881080000000 186M RW PSE
GLB NX pmd ---> wrong
0xffff881080000000-0xffff888000000000 446G pud
0xffff888000000000-0xffffc20000000000 58880G pgd
===>
0xffff881040000000-0xffff881074400000 836M RW PSE GLB NX pmd
0xffff881074400000-0xffff8810744a0000 640K RW GLB NX pte
0xffff8810744a0000-0xffff8810744b0000 64K RW PCD GLB NX pte
0xffff8810744b0000-0xffff881074600000 1344K RW GLB NX pte
0xffff881074600000-0xffff881078000000 58M RW PSE GLB NX pmd
0xffff881078000000-0xffff881080000000 128M pmd
0xffff881080000000-0xffff888000000000 446G pud
0xffff888000000000-0xffffc20000000000 58880G pgd

YH
--
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/