« Previous | Next » 

Revision b8cc45d6

IDb8cc45d6a6f7b6607d5c55817d674f3e5f92ff70

Added by Glauber Costa almost 11 years ago

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 <>
CC: Jan Kiszka <>
Signed-off-by: Marcelo Tosatti <>

Files

  • added
  • modified
  • copied
  • renamed
  • deleted

View differences