diff options
author | 2016-09-01 14:21:03 +0200 | |
---|---|---|
committer | 2016-09-20 09:26:15 +0200 | |
commit | 108b249c453dd7132599ab6dc7e435a7036c193f (patch) | |
tree | eb600c0558d7032bc1b0c62066f74ac109bd4fd7 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | KVM: x86: initialize kvmclock_offset (diff) | |
download | linux-dev-108b249c453dd7132599ab6dc7e435a7036c193f.tar.xz linux-dev-108b249c453dd7132599ab6dc7e435a7036c193f.zip |
KVM: x86: introduce get_kvmclock_ns
Introduce a function that reads the exact nanoseconds value that is
provided to the guest in kvmclock. This crystallizes the notion of
kvmclock as a thin veneer over a stable TSC, that the guest will
(hopefully) convert with NTP. In other words, kvmclock is *not* a
paravirtualized host-to-guest NTP.
Drop the get_kernel_ns() function, that was used both to get the base
value of the master clock and to get the current value of kvmclock.
The former use is replaced by ktime_get_boot_ns(), the latter is
the purpose of get_kernel_ns().
This also allows KVM to provide a Hyper-V time reference counter that
is synchronized with the time that is computed from the TSC page.
Reviewed-by: Roman Kagan <rkagan@virtuozzo.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions