On Mon, May 09, 2016 at 03:44:57PM +0200, Paolo Bonzini wrote: [...] > 2) KVM doesn't yet expose any XSAVES state save component, and the only > one defined in Skylake (processor tracing) probably will block migration > and will have to be added separately. > [...] > Item number 2 on the other hand means that it's okay to add Skylake CPU > models without XSAVES. Because of the large number of kernels in the > wild that block XSAVES, I'm inclined to do that. Agreed. Now, should we name the CPU model without XSAVES "Skylake" or "Skylake-noXSAVES"? I'm inclined towards the latter, to follow the same pattern we used for "Haswell-noTSX". -- Eduardo -- 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
