Re: TSC deadline timer in guests vs. migration?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Jul 05, 2016 at 11:40:22PM +0200, Paolo Bonzini wrote:
> 
> 
> On 05/07/2016 20:11, Eduardo Habkost wrote:
> > In this case, if TSC scaling is not supported, is it preferable
> > to have the TSC frequency suddenly changing without the guest
> > being aware of it, or to run in tsc_always_catchup mode? QEMU 2.5
> > did the former, QEMU 2.6 does the latter.
> 
> I suspect the former is better just because we don't know the exact
> effect of tsc_always_catchup.

Forget what I said. QEMU 2.6 checks for KVM_CAP_TSC_CONTROL
before calling KVM_SET_TSC_KHZ. In this case, it will never
trigger tsc_always_catchup, right?

-- 
Eduardo
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux