Eric Lee / smarc-fsl-linux-kernel

05 Aug, 2011

1 commit

22 Jul, 2011

1 commit

  • aafade242   x86-64, vdso: Do not allocate memory for the vDSO ... Browse Code »

    We can map the vDSO straight from kernel data, saving a few page
    allocations. As an added bonus, the deleted code contained a memory
    leak.

    Signed-off-by: Andy Lutomirski
    Link: http://lkml.kernel.org/r/2c4ed5c2c2e93603790229e0c3403ae506ccc0cb.1311277573.git.luto@mit.edu
    Signed-off-by: H. Peter Anvin

    Andy Lutomirski
     

29 Apr, 2008

1 commit

  • d9dedc138   x86_64 vDSO: use initdata ... Browse Code »

    The 64-bit vDSO image is in a special ".vdso" section for no reason
    I can determine. Furthermore, the location of the vdso_end symbol
    includes some wrongly-calculated padding space in the image, which
    is then (correctly) rounded to page size, resulting in an extra page
    of zeros in the image mapped in to user processes.

    This changes it to put the vdso.so image into normal initdata as we
    have always done for the 32-bit vDSO images. The extra padding is
    gone, so the user VMA is one page instead of two. The image that
    was already copied around at boot time is now in initdata, so we
    recover that wasted space after boot.

    Signed-off-by: Roland McGrath
    Signed-off-by: Linus Torvalds

    Roland McGrath
     

11 Oct, 2007

1 commit