From: Avi Kivity a...@redhat.com
Signed-off-by: Avi Kivity a...@redhat.com
diff --git a/linux-2.6 b/linux-2.6
index 1374571..5383e99 16
--- a/linux-2.6
+++ b/linux-2.6
@@ -1 +1 @@
-Subproject commit 1374571813a9e30e65c5274aa9fdff15f2c58ee2
+Subproject commit
From: Avi Kivity a...@redhat.com
Signed-off-by: Avi Kivity a...@redhat.com
diff --git a/x86/Kbuild b/x86/Kbuild
index c4694a7..66e23a0 100644
--- a/x86/Kbuild
+++ b/x86/Kbuild
@@ -3,7 +3,7 @@
include $(obj)/../config.kbuild
obj-m := kvm.o kvm-intel.o kvm-amd.o
-kvm-objs := kvm_main.o x86.o
From: Anthony Liguori aligu...@us.ibm.com
According to 16.2.5 in the SDM, eflags.vm in the tss is consulted before loading
and new segments. If eflags.vm == 1, then the segments are treated as 16-bit
segments. The LDTR and TR are not normally available in vm86 mode so if they
happen to somehow
From: Avi Kivity a...@redhat.com
We're in arch/x86, what could we possibly be emulating?
Signed-off-by: Avi Kivity a...@redhat.com
diff --git a/arch/x86/include/asm/kvm_x86_emulate.h
b/arch/x86/include/asm/kvm_emulate.h
similarity index 100%
rename from arch/x86/include/asm/kvm_x86_emulate.h