On 20/05/2016 08:03, Jan Kiszka wrote: > IIRC, VMX preemption timer was broken on several older CPUs. That was > one reason we didn't use it to emulated nested preemption timer. Were > all those CPUs also not exposing the TCP deadline timer? > > In any case, just checking for the feature bit like you do in patch 2 > shouldn't be enough to catch those CPUs. Or were there microcode patches > distributed by now that translated the errata into bit removals? Yes, we need to include the list of affected CPU steppings (VirtualBox has it). Leaving this out is fine for an RFC, though. Thanks, Paolo -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
