Ladi Prosek a826faf108 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>		2017-07-13 17:25:39 +02:00
..
asm	KVM: x86: make backwards_tsc_observed a per-VM variable	2017-07-13 17:25:39 +02:00
uapi/asm	pci-v4.13-changes	2017-07-08 15:51:57 -07:00