diff options
| author | Lei Chen <lei.chen@smartx.com> | 2025-08-19 23:20:27 +0800 |
|---|---|---|
| committer | Sean Christopherson <seanjc@google.com> | 2025-11-17 07:50:25 -0800 |
| commit | e78fb96b41c6ac85c1a02c7e9610d1ebaa9b5d98 (patch) | |
| tree | 1b26f1b59b231aeff971d840595a0f415570b644 | |
| parent | 446fcce2a52b533c543dabba26777813c347577c (diff) | |
KVM: x86: remove comment about ntp correction sync for
Since vcpu local clock is no longer affected by ntp,
remove comment about ntp correction sync for function
kvm_gen_kvmclock_update.
Signed-off-by: Lei Chen <lei.chen@smartx.com>
Link: https://patch.msgid.link/20250819152027.1687487-4-lei.chen@smartx.com
Signed-off-by: Sean Christopherson <seanjc@google.com>
| -rw-r--r-- | arch/x86/kvm/x86.c | 4 |
1 files changed, 1 insertions, 3 deletions
diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c index 33fcd79e33da..03b2121069c4 100644 --- a/arch/x86/kvm/x86.c +++ b/arch/x86/kvm/x86.c @@ -3518,9 +3518,7 @@ uint64_t kvm_get_wall_clock_epoch(struct kvm *kvm) /* * kvmclock updates which are isolated to a given vcpu, such as * vcpu->cpu migration, should not allow system_timestamp from - * the rest of the vcpus to remain static. Otherwise ntp frequency - * correction applies to one vcpu's system_timestamp but not - * the others. + * the rest of the vcpus to remain static. * * So in those cases, request a kvmclock update for all vcpus. * The worst case for a remote vcpu to update its kvmclock |