aboutsummaryrefslogtreecommitdiff
path: root/target-i386/cpu.h
diff options
context:
space:
mode:
authorGlauber Costa <glommer@redhat.com>2011-02-03 14:19:53 -0500
committerMarcelo Tosatti <mtosatti@redhat.com>2011-02-14 12:39:46 -0200
commitb8cc45d6a6f7b6607d5c55817d674f3e5f92ff70 (patch)
tree6c48088104c0a82dafed244598b8154613447302 /target-i386/cpu.h
parentcdea50ede1b8a2efe989fafc57260053b180219f (diff)
downloadqemu-b8cc45d6a6f7b6607d5c55817d674f3e5f92ff70.zip
qemu-b8cc45d6a6f7b6607d5c55817d674f3e5f92ff70.tar.gz
qemu-b8cc45d6a6f7b6607d5c55817d674f3e5f92ff70.tar.bz2
kvm: make tsc stable over migration and machine start
If the machine is stopped, we should not record two different tsc values upon a save operation. The same problem happens with kvmclock. But kvmclock is taking a different diretion, being now seen as a separate device. Since this is unlikely to happen with the tsc, I am taking the approach here of simply registering a handler for state change, and using a per-CPUState variable that prevents double updates for the TSC. Signed-off-by: Glauber Costa <glommer@redhat.com> CC: Jan Kiszka <jan.kiszka@web.de> Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
Diffstat (limited to 'target-i386/cpu.h')
-rw-r--r--target-i386/cpu.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/target-i386/cpu.h b/target-i386/cpu.h
index af701a4..5f1df8b 100644
--- a/target-i386/cpu.h
+++ b/target-i386/cpu.h
@@ -734,6 +734,7 @@ typedef struct CPUX86State {
uint32_t sipi_vector;
uint32_t cpuid_kvm_features;
uint32_t cpuid_svm_features;
+ bool tsc_valid;
/* in order to simplify APIC support, we leave this pointer to the
user */