1. 06 Oct, 2010 2 commits
    • Yinghai Lu's avatar
      x86-32, memblock: Make add_highpages honor early reserved ranges · 1d931264
      Yinghai Lu authored
      Originally the only early reserved range that is overlapped with high
      pages is "KVA RAM", but we already do remove that from the active ranges.
      
      However, It turns out Xen could have that kind of overlapping to support memory
      ballooning.x
      
      So we need to make add_highpage_with_active_regions() to subtract
      memblock reserved just like low ram; this is the proper design anyway.
      
      In this patch, refactering get_freel_all_memory_range() to make it can
      be used by add_highpage_with_active_regions().  Also we don't need to
      remove "KVA RAM" from active ranges.
      Signed-off-by: default avatarYinghai Lu <yinghai@kernel.org>
      LKML-Reference: <4CABB183.1040607@kernel.org>
      Signed-off-by: default avatarH. Peter Anvin <hpa@zytor.com>
      1d931264
    • Yinghai Lu's avatar
      x86, memblock: Fix crashkernel allocation · 9f4c1396
      Yinghai Lu authored
      Cai Qian found crashkernel is broken with the x86 memblock changes.
      
      1. crashkernel=128M@32M always reported that range is used, even if
         the first kernel is small and does not usethat range
      
      2. we always got following report when using "kexec -p"
      	Could not find a free area of memory of a000 bytes...
      	locate_hole failed
      
      The root cause is that generic memblock_find_in_range() will try to
      allocate from the top of the range, whereas the kexec code was written
      assuming that allocation was always near the bottom and that it could
      blindly extend memory upward.  Unfortunately the kexec code doesn't
      have a system for requesting the range that it really needs, so this
      is subject to probabilistic failures.
      
      This patch hacks around the problem by limiting the target range
      heuristically to below the traditional bzImage max range.  This number
      is arbitrary and not always correct, and a much better result would be
      obtained by having kexec communicate this number based on the kernel
      header information and any appropriate command line options.
      Reported-and-Bisected-by: default avatarCAI Qian <caiqian@redhat.com>
      Signed-off-by: default avatarYinghai Lu <yinghai@kernel.org>
      LKML-Reference: <4CABAF2A.5090501@kernel.org>
      Cc: Vivek Goyal <vgoyal@redhat.com>
      Signed-off-by: default avatarH. Peter Anvin <hpa@zytor.com>
      9f4c1396
  2. 16 Sep, 2010 1 commit
    • Yinghai Lu's avatar
      arm, memblock: Fix the sparsemem build · 7c996361
      Yinghai Lu authored
      Stephen Rothwell reported this build failure:
      
        arch/arm/mm/init.c: In function 'arm_memory_present':
        arch/arm/mm/init.c:260: warning: ISO C90 forbids mixed declarations and code
      
      Caused by commit 719c1514 ("memblock/arm: Use new accessors")
      which forgot a closing brace on a new for_each_memblock() in
      arm_memory_present().
      Reported-by: default avatarStephen Rothwell <sfr@canb.auug.org.au>
      Signed-off-by: default avatarYinghai Lu <yinghai@kernel.org>
      Cc: Peter Zijlstra <peterz@infradead.org>
      Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
      Cc: Russell King <linux@arm.linux.org.uk>
      LKML-Reference: <4C91C544.5050907@kernel.org>
      Signed-off-by: default avatarIngo Molnar <mingo@elte.hu>
      7c996361
  3. 15 Sep, 2010 1 commit
  4. 11 Sep, 2010 2 commits
  5. 31 Aug, 2010 1 commit
  6. 29 Aug, 2010 3 commits
  7. 28 Aug, 2010 28 commits
  8. 27 Aug, 2010 2 commits