Virtualization - Apr 2007 - Why disable vdso by default with CONFIG_PARAVIRT?

On Tuesday 12 December 2006 02:22, Jeremy Fitzhardinge
wrote:
> What problem do they cause together?  There's certainly no problem with
> Xen+vdso
This was the change which finally got my test system (with an older
SUSE 9.0 based user land to boot).  With paravirt older glibc's ld.so 
otherwise throws assertation failures because it somehow can't deal with 
the new placement. This only happens with paravirt enabled.

Binary compatibility is important.
> (in fact, its actually very useful so that it picks up the
> right libc with Xen-friendly TLS).
AFAIK libc selection comes from the aux vector, not the vdso.

-Andi

Jeremy Fitzhardinge wrote:
> Hi Andi,
>
> What problem do they cause together?  There's certainly no problem with
> Xen+vdso (in fact, its actually very useful so that it picks up the
> right libc with Xen-friendly TLS).
>   
Methinks the compat VDSO support got broken in the config?  Paravirt + 
COMPAT_VDSO are incompatible.

Hi Andi,

What problem do they cause together?  There's certainly no problem with
Xen+vdso (in fact, its actually very useful so that it picks up the
right libc with Xen-friendly TLS).

    J