Ian Campbell 5dc64a3442 xen: do not reserve 2 pages of padding between hypervisor and fixmap. ... When reserving space for the hypervisor the Xen paravirt backend adds an extra two pages (this was carried forward from the 2.6.18-xen tree which had them "for safety"). Depending on various CONFIG options this can cause the boot time fixmaps to span multiple PMDs which is not supported and triggers a WARN in early_ioremap_init(). This was exposed by 2216d199b1 which moved the dmi table parsing earlier. x86: fix CONFIG_X86_RESERVE_LOW_64K=y The bad_bios_dmi_table() quirk never triggered because we do DMI setup too late. Move it a bit earlier. There is no real reason to reserve these two extra pages and the fixmap already incorporates FIX_HOLE which serves the same purpose. None of the other callers of reserve_top_address do this. Signed-off-by: Ian Campbell <ian.campbell@citrix.com> Signed-off-by: Ingo Molnar <mingo@elte.hu>		2008-10-10 13:00:15 +02:00
..
debugfs.c
debugfs.h
enlighten.c	xen: do not reserve 2 pages of padding between hypervisor and fixmap.	2008-10-10 13:00:15 +02:00
grant-table.c
irq.c
Kconfig
Makefile
mmu.c
mmu.h
multicalls.c
multicalls.h
setup.c
smp.c
spinlock.c
suspend.c
time.c
vdso.h
xen-asm_32.S
xen-asm_64.S
xen-head.S
xen-ops.h