On 02/01/2012 01:00 PM, Marcelo Tosatti wrote: > On Wed, Feb 01, 2012 at 12:27:00PM +0200, Avi Kivity wrote: > > If the guest thinks it's an AMD, it will not have prepared the SYSENTER MSRs, > > and if the guest executes SYSENTER in compatibility mode, it will fails. > > > > Detect this condition and #UD instead, like the spec says. > > Note the SYSENTER_CS & 0xfffc == 0 check protects against a fatal error (unlike > the SYSCALL bug), in case of zeroed MSRs. That's a relief. It's still possible for this to fail (say kexec from 32-bit guest to 64-bit guest) but it's incredibly unlikely. -- error compiling committee.c: too many arguments to function -- 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
