Andi Kleen wrote: > The boot option is already there, but boot options for is not my > idea of user friendly binary compatibility. > Yes, not friendly. Perhaps we can reverse the boot option? I.e make vdso_enable=force re-activate the vdso even if it gets moved by a hypervisor and COMPAT_VDSO was compiled in. But how many actual users are affected by these old glibc's that we need to care so much about them running new technology, especially if that technology can be built with the ability to warn them that they probably need to boot with vdso=disabled? >> and a printk warning if you take #GPs and kill the init >> proc, because for us, this is not an expected support scenario. We >> would much rather support the VDSO by default in paravirt kernels even >> with COMPAT_VDSO turned on. >> > > But you can't have it at the compatible fixed address, right? > While technically possible, is is not possible to do that anytime soon, and the drawbacks might overshadow the performance gain of the VDSO - and I don't think any of the other hypervisors (lhype, Xen) will be able to do that either. KVM can do it, only because it relies on hardware virt. Zach
