[lkml]   [2003]   [Jan]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: vmalloc/module_alloc: unable to handle two memory regions
    On Fri, Jan 31, 2003 at 02:48:20AM -0800, Andrew Morton wrote:
    > Boggle.
    > Isn't this totally abusing get_vma_area?
    > What stops an ioremap region from landing in module space?

    Exactly the problem.

    What's more is that fs/proc/kcore.c:get_kcore_size() also breaks, so
    this isn't an acceptable solution. get_kcore_size wants the module
    region to be above PAGE_OFFSET.

    In order to place the module in the normal vmalloc space, we end up with
    a chicken and egg problem - we need to scan the module from kernel space
    to find out how large to make the jump table, but we can't because the
    module hasn't been loaded into kernel memory - this is the reason why it
    was suggested to go down this route.

    Russell King ( The developer of ARM Linux

    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: 2005-03-22 13:32    [W:0.020 / U:83.900 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site