[lkml]   [2012]   [Jun]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: Early boot panic on machine with lots of memory
    Hello, Yinghai.

    On Thu, Jun 21, 2012 at 06:47:24PM -0700, Yinghai Lu wrote:
    > > I'm afraid this is too early.  We don't want the region to be unmapped
    > > yet.  This should only happen after all memblock usages are finished
    > > which I don't think is the case yet.
    > No, it is not early. at that time memblock usage is done.
    > Also I tested one system with huge memory, duplicated the problem on
    > KVM that Sasha met.
    > my patch fixes the problem.
    > please check attached patch.
    > Also I add another patch to double check if there is any reference
    > with reserved.region.
    > so far there is no reference found.

    Thanks for checking it. I was worried because of the re-reservation
    of reserved.regions after giving memory to the page allocator -
    ie. memblock_reserve_reserved_regions() call. If memblock is done at
    that point, there's no reason to have that call at all. It could be
    that that's just dead code. If so, why aren't we freeing
    memory.regions? Also, shouldn't we be clearing
    memblock.cnt/max/total_size/regions so that we know for sure that it's
    never used again? What am I missing?


    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2012-06-22 21:41    [W:0.031 / U:15.668 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site