summaryrefslogtreecommitdiffstats
path: root/mm/Kconfig
diff options
context:
space:
mode:
authorH. Peter Anvin <hpa@zytor.com>2008-01-30 13:32:51 +0100
committerIngo Molnar <mingo@elte.hu>2008-01-30 13:32:51 +0100
commitcf8fa920cb4271f17e0265c863d64bea1b31941a (patch)
tree5a036d33e78108c9a762913155823ff0c91051f5 /mm/Kconfig
parent6d7d7433750c7c6eec93d7b3206019e329228686 (diff)
downloadblackbird-op-linux-cf8fa920cb4271f17e0265c863d64bea1b31941a.tar.gz
blackbird-op-linux-cf8fa920cb4271f17e0265c863d64bea1b31941a.zip
i386: handle an initrd in highmem (version 2)
The boot protocol has until now required that the initrd be located in lowmem, which makes the lowmem/highmem boundary visible to the boot loader. This was exported to the bootloader via a compile-time field. Unfortunately, the vmalloc= command-line option breaks this part of the protocol; instead of adding yet another hack that affects the bootloader, have the kernel relocate the initrd down below the lowmem boundary inside the kernel itself. Note that this does not rely on HIGHMEM being enabled in the kernel. Signed-off-by: H. Peter Anvin <hpa@zytor.com> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'mm/Kconfig')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud