Rusty Russell 66aee91aaa 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>		2007-10-13 10:18:18 +02:00
..
Kconfig	KVM: Fix virtualization menu help text	2007-09-22 12:55:18 -07:00
kvm_main.c	KVM: Use standard CR4 flags, tighten checking	2007-10-13 10:18:18 +02:00
kvm_svm.h	KVM: SVM: Only save/restore MSRs when needed	2007-05-03 10:52:32 +03:00
kvm.h	KVM: Use standard CR4 flags, tighten checking	2007-10-13 10:18:18 +02:00
Makefile
mmu.c	KVM: Trivial: Use standard CR0 flags macros from asm/cpu-features.h	2007-10-13 10:18:18 +02:00
paging_tmpl.h	KVM: Use standard CR3 flags, tighten checking	2007-10-13 10:18:18 +02:00
segment_descriptor.h
svm.c	KVM: Use standard CR4 flags, tighten checking	2007-10-13 10:18:18 +02:00
svm.h	KVM: SVM: Reliably detect if SVM was disabled by BIOS	2007-07-16 12:05:49 +03:00
vmx.c	KVM: Use standard CR4 flags, tighten checking	2007-10-13 10:18:18 +02:00
vmx.h	KVM: Use standard CR4 flags, tighten checking	2007-10-13 10:18:18 +02:00
x86_emulate.c	KVM: Trivial: Comment spelling may escape grep	2007-10-13 10:18:18 +02:00
x86_emulate.h	KVM: Trivial: Make decode_register() static	2007-10-13 10:18:18 +02:00