KVM: Use standard CR4 flags, tighten checking
commit66aee91aaab8f998d28a61ed7733be17ad8e6d8f
authorRusty Russell <rusty@rustcorp.com.au>
Tue, 17 Jul 2007 13:34:16 +0000 (17 23:34 +1000)
committerAvi Kivity <avi@qumranet.com>
Sat, 13 Oct 2007 08:18:18 +0000 (13 10:18 +0200)
treef3cd552c4a176cbba0929788b03867cb33d7b5b5
parentf802a307cb2cabdd0c6b48067dbe901d6fe27246
KVM: Use standard CR4 flags, tighten checking

On this machine (Intel), writing to the CR4 bits 0x00000800 and
0x00001000 cause a GPF.  The Intel manual is a little unclear, but
AFIACT they're reserved, too.

Also fix spelling of CR4_RESEVED_BITS.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Signed-off-by: Avi Kivity <avi@qumranet.com>
drivers/kvm/kvm.h
drivers/kvm/kvm_main.c
drivers/kvm/svm.c
drivers/kvm/vmx.c
drivers/kvm/vmx.h