diff options
| author | David Woodhouse <dwmw@amazon.co.uk> | 2026-08-26 14:32:52 -0700 |
|---|---|---|
| committer | Sean Christopherson <seanjc@google.com> | 2026-09-11 11:46:18 -0700 |
| commit | c56419275caad2d99264b7c50b0701552ed3ef75 (patch) | |
| tree | 87cab31731f3c40a013f7a1ddaa88b9b31a806bb /tools/perf/scripts/python/task-analyzer.py | |
| parent | abdef42276d88417f6a0c1f9fae8190accc3bc38 (diff) | |
KVM: x86: Use get_kvmclock() in kvm_get_wall_clock_epoch()
Now that get_kvmclock() correctly handles TSC scaling and captures both
wallclock and kvmclock from the same TSC reading,
kvm_get_wall_clock_epoch() can simply call it instead of duplicating
the pvclock computation.
This eliminates the last instance of the "definition C" kvmclock
calculation — as described in commit 633d7652f80f ("KVM: x86/xen: Do not
corrupt KVM clock in kvm_xen_shared_info_init()") — which computed
nanoseconds directly from the host TSC without accounting for guest TSC
scaling.
Signed-off-by: David Woodhouse <dwmw@amazon.co.uk>
Link: https://patch.msgid.link/20260826213303.914988-13-seanjc@google.com
Signed-off-by: Sean Christopherson <seanjc@google.com>
Diffstat (limited to 'tools/perf/scripts/python/task-analyzer.py')
0 files changed, 0 insertions, 0 deletions
