Commit-ID: 6abf65510944d33b47575d151c6b318993c8d2b5 Gitweb: http://git.kernel.org/tip/6abf65510944d33b47575d151c6b318993c8d2b5 Author: Jan Beulich <JBeulich@xxxxxxxxxx> AuthorDate: Thu, 30 Jul 2009 16:49:30 +0100 Committer: Ingo Molnar <mingo@xxxxxxx> CommitDate: Tue, 4 Aug 2009 16:27:29 +0200 x86, 32-bit: Fix double accounting in reserve_top_address() With VMALLOC_END included in the calculation of MAXMEM (as of 2.6.28) it is no longer correct to also bump __VMALLOC_RESERVE in reserve_top_address(). Doing so results in needlessly small lowmem. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxxxx> LKML-Reference: <4A71DD2A020000780000D482@xxxxxxxxxxxxxxxxxx> Signed-off-by: Ingo Molnar <mingo@xxxxxxx> --- arch/x86/mm/pgtable.c | 1 - 1 files changed, 0 insertions(+), 1 deletions(-) diff --git a/arch/x86/mm/pgtable.c b/arch/x86/mm/pgtable.c index af8f965..ed34f5e 100644 --- a/arch/x86/mm/pgtable.c +++ b/arch/x86/mm/pgtable.c @@ -329,7 +329,6 @@ void __init reserve_top_address(unsigned long reserve) printk(KERN_INFO "Reserving virtual address space above 0x%08x\n", (int)-reserve); __FIXADDR_TOP = -reserve - PAGE_SIZE; - __VMALLOC_RESERVE += reserve; #endif } -- To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|