lkml.org 
[lkml]   [2007]   [Mar]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [patch] paravirt: VDSO page is essential
    Ingo Molnar wrote:
    > there's no need to disable the VDSO for old userspace ...
    >

    Well, apart from the obvious question to which nobody actually knows the
    answer, (how many people run old user space that required
    CONFIG_COMPAT_VDSO), what do you think of reversing the boot option?

    vdso=enabled (default - turn on VDSO on normal boots)
    vdso=disabled (turn off VDSO unconditionally)
    [vdso=compat] (default for COMPAT_VDSO - keep VDSO only when mapped at
    compat location. Note the option is not required to be implemented
    because it is logically implied from vdso=enabled && COMPAT_VDSO and the
    default boot behavior)
    vdso=force (keep VDSO even when moved to a new location and COMPAT_VDSO
    is enabled).

    In our case, installing VMware tools in the guest would then detect if
    userspace supports VDSO or if it requires COMPAT_VDSO and would then set
    boot parameters for the kernel appropriately. And the native boot and
    kvm paravirt-ops boot are completely unaffected.

    Zach
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2007-03-05 21:45    [W:0.019 / U:1.336 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site