diff options
| author | Marcelo Tosatti <mtosatti@redhat.com> | 2019-01-04 18:54:14 +0100 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2019-02-20 22:48:52 +0100 |
| commit | 7539b174aef405d9d57db48c58390ba360c91312 (patch) | |
| tree | 6eeb5f8ee1e0d8a99769abde4741588f444eb6aa /virt | |
| parent | KVM: Never start grow vCPU halt_poll_ns from value below halt_poll_ns_grow_start (diff) | |
| download | linux-7539b174aef405d9d57db48c58390ba360c91312.tar.xz linux-7539b174aef405d9d57db48c58390ba360c91312.zip | |
x86: kvmguest: use TSC clocksource if invariant TSC is exposed
The invariant TSC bit has the following meaning:
"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."
IOW, TSC does not change frequency. In such case, and with
TSC scaling hardware available to handle migration, it is possible
to use the TSC clocksource directly, whose system calls are
faster.
Reduce the rating of kvmclock clocksource to allow TSC clocksource
to be the default if invariant TSC is exposed.
Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
v2: Use feature bits and tsc_unstable() check (Sean Christopherson)
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'virt')
0 files changed, 0 insertions, 0 deletions