Paravirt-ops VMI / Xen / lrustyvisor merge status

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 2007-02-08 at 22:59 -0800, Zachary Amsden wrote:
> I believe there was a patch that got applied that turned it off by 
> default if CONFIG_PARAVIRT was enabled.  Doing it the cpuid way is the 
> right solution, IMHO.

Ah, yes, the VDSO issue.  This is separate, and does need fixing. 

Basically, if the user doesn't select COMPAT_VDSO, we don't have a
problem.  Currently they don't get offered COMPAT_VDSO if PARAVIRT is
enabled, but we *still* disable vdso in that case (unless vdso=1 is on
cmdline).

I think the best choice is to rework COMPAT_VDSO to a general "support
old glibcs" option, which will either (1) map it fixed if !
CONFIG_PARAVIRT, or (2) disable it if CONFIG_PARAVIRT.

I'll send that soon...

Cheers,
Rusty.




[Index of Archives]     [KVM Development]     [Libvirt Development]     [Libvirt Users]     [CentOS Virtualization]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite Forum]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux