[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] invtsc + migration + TSC scaling
From: |
Eduardo Habkost |
Subject: |
[Qemu-devel] invtsc + migration + TSC scaling |
Date: |
Fri, 14 Oct 2016 18:20:31 -0300 |
User-agent: |
Mutt/1.7.0 (2016-08-17) |
I have been wondering: should we allow live migration with the
invtsc flag enabled, if TSC scaling is available on the
destination?
For reference, this is what the Intel SDM says about invtsc:
The time stamp counter in newer processors may support an
enhancement, referred to as invariant TSC. Processor’s support
for invariant TSC is indicated by CPUID.80000007H:EDX[8].
The invariant TSC will run at a constant rate in all ACPI P-,
C-. and T-states. This is the architectural behavior moving
forward. On processors with invariant TSC support, the OS may
use the TSC for wall clock timer services (instead of ACPI or
HPET timers). TSC reads are much more efficient and do not
incur the overhead associated with a ring transition or access
to a platform resource.
--
Eduardo
- [Qemu-devel] invtsc + migration + TSC scaling,
Eduardo Habkost <=
- Re: [Qemu-devel] invtsc + migration + TSC scaling, Marcelo Tosatti, 2016/10/17
- Re: [Qemu-devel] invtsc + migration + TSC scaling, Radim Krčmář, 2016/10/17
- Re: [Qemu-devel] invtsc + migration + TSC scaling, Paolo Bonzini, 2016/10/17
- Re: [Qemu-devel] invtsc + migration + TSC scaling, Eduardo Habkost, 2016/10/17
- Re: [Qemu-devel] invtsc + migration + TSC scaling, Marcelo Tosatti, 2016/10/17
- Re: [Qemu-devel] invtsc + migration + TSC scaling, Paolo Bonzini, 2016/10/18
- Re: [Qemu-devel] invtsc + migration + TSC scaling, Marcelo Tosatti, 2016/10/18
- Re: [Qemu-devel] invtsc + migration + TSC scaling, Radim Krčmář, 2016/10/18
- Re: [Qemu-devel] invtsc + migration + TSC scaling, Eduardo Habkost, 2016/10/18
- Re: [Qemu-devel] invtsc + migration + TSC scaling, Radim Krčmář, 2016/10/19