[lkml]   [2008]   [Dec]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH] Fix VMI crash on boot in 2.6.27+ kernels
    On Wed, 2008-12-10 at 16:20 -0800, Yinghai Lu wrote:
    > it seems still have some problem.
    > you moved reserve_top_address before parse_parameter...

    I really only care about resetting fixmap_top. Adding more vmalloc
    space to accomodate what we stole is just being nice... in practice this
    should not be a problem.

    > __VMALLOC_RESERVE will be overwriten by vmalloc=...
    > you may need to split reserve_top_address() to two functions...

    For now, misuse vmalloc=XXX at your own risk - why the need for it

    I agree, it should be cleaned up, as HPA suggests, we should move the
    fixmap to a fixed place anyways, and have vmalloc area from the top of
    linear memory down to the end of the physical memory mapping. But there
    really isn't time to do anything better for 2.6.28.


     \ /
      Last update: 2008-12-11 05:53    [W:0.020 / U:2.628 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site