On Tue, Jan 13, 2009 at 11:27:07AM +0200, Avi Kivity wrote: > Amit Shah wrote: >> CPUID functions 4, 0xb and 0xd behave differently for different values of >> ECX. >> Store these values if userspace passes them. >> > > Userspace has no way of knowing whether the kernel contains this fix or not. > > Use the SET_CPUID2 interface instead.
OK; So first attempt to use the SET_CPUID2 interface. If that fails (new userspace on older kernel), what should we do? Amit -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
