diff options
| author | Ladi Prosek <lprosek@redhat.com> | 2017-06-26 09:56:43 +0200 |
|---|---|---|
| committer | Radim Krčmář <rkrcmar@redhat.com> | 2017-07-13 17:25:39 +0200 |
| commit | a826faf108e2d855929342268e68c43ba667379a (patch) | |
| tree | 1ff5da7c983841535db6088b05facbbfba7c876e /include | |
| parent | KVM: trigger uevents when creating or destroying a VM (diff) | |
| download | linux-a826faf108e2d855929342268e68c43ba667379a.tar.xz linux-a826faf108e2d855929342268e68c43ba667379a.zip | |
KVM: x86: make backwards_tsc_observed a per-VM variable
The backwards_tsc_observed global introduced in commit 16a9602 is never
reset to false. If a VM happens to be running while the host is suspended
(a common source of the TSC jumping backwards), master clock will never
be enabled again for any VM. In contrast, if no VM is running while the
host is suspended, master clock is unaffected. This is inconsistent and
unnecessarily strict. Let's track the backwards_tsc_observed variable
separately and let each VM start with a clean slate.
Real world impact: My Windows VMs get slower after my laptop undergoes a
suspend/resume cycle. The only way to get the perf back is unloading and
reloading the kvm module.
Signed-off-by: Ladi Prosek <lprosek@redhat.com>
Signed-off-by: Radim Krčmář <rkrcmar@redhat.com>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions