From: Marcelo Tosatti <mtosatti@redhat.com>
To: kvm-devel <kvm@vger.kernel.org>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>
Subject: [PATCH] KVM: x86: fix KVM_SET_CLOCK relative to setting correct clock value
Date: Tue, 2 May 2017 18:36:16 -0300 [thread overview]
Message-ID: <20170502213616.GA24837@amt.cnet> (raw)
In the masterclock enabled case, kvmclock_offset must be adjusted so
that user_ns.clock = master_kernel_ns + kvmclock_offset (that is, the
value set from KVM_SET_CLOCK is the one visible at system_timestamp).
This way the guest clock:
1. Starts counting when KVM_SET_CLOCK executes.
2. With the value provided by userspace.
Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
---
arch/x86/kvm/x86.c | 23 ++++++++++++++++++++---
1 file changed, 20 insertions(+), 3 deletions(-)
Index: kvm/arch/x86/kvm/x86.c
===================================================================
--- kvm.orig/arch/x86/kvm/x86.c 2017-04-27 17:37:48.131348255 -0300
+++ kvm/arch/x86/kvm/x86.c 2017-04-27 17:56:58.397530444 -0300
@@ -4172,8 +4172,9 @@
break;
}
case KVM_SET_CLOCK: {
- struct kvm_clock_data user_ns;
u64 now_ns;
+ struct kvm_clock_data user_ns;
+ struct kvm_arch *ka = &kvm->arch;
r = -EFAULT;
if (copy_from_user(&user_ns, argp, sizeof(user_ns)))
@@ -4184,9 +4185,25 @@
goto out;
r = 0;
- now_ns = get_kvmclock_ns(kvm);
- kvm->arch.kvmclock_offset += user_ns.clock - now_ns;
+
kvm_gen_update_masterclock(kvm);
+ if (ka->use_master_clock) {
+ /*
+ * In the masterclock enabled case,
+ * kvmclock_offset must be adjusted so that
+ * user_ns.clock = master_kernel_ns + kvmclock_offset
+ * (that is, the value set from KVM_SET_CLOCK is the
+ * one visible at system_timestamp).
+ */
+ kvm->arch.kvmclock_offset = user_ns.clock -
+ ka->master_kernel_ns;
+
+ kvm_for_each_vcpu(i, vcpu, kvm)
+ kvm_make_request(KVM_REQ_CLOCK_UPDATE, vcpu);
+ } else {
+ now_ns = get_kvmclock_ns(kvm);
+ kvm->arch.kvmclock_offset += user_ns.clock - now_ns;
+ }
break;
}
case KVM_GET_CLOCK: {
next reply other threads:[~2017-05-02 21:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 21:36 Marcelo Tosatti [this message]
2017-05-03 13:08 ` [PATCH] KVM: x86: fix KVM_SET_CLOCK relative to setting correct clock value Paolo Bonzini
2017-05-03 13:40 ` Marcelo Tosatti
2017-05-03 13:55 ` Paolo Bonzini
2017-05-03 18:24 ` Marcelo Tosatti
2017-05-03 13:43 ` [PATCH v2] " Marcelo Tosatti
2017-05-10 18:04 ` Radim Krčmář
2017-05-11 15:39 ` Marcelo Tosatti
2017-05-12 14:13 ` Radim Krčmář
2017-05-12 14:36 ` Paolo Bonzini
2017-05-12 15:31 ` Marcelo Tosatti
2017-05-12 17:37 ` Radim Krčmář
2017-05-13 3:46 ` Marcelo Tosatti
2017-05-15 16:19 ` Radim Krčmář
2017-05-15 21:06 ` Marcelo Tosatti
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170502213616.GA24837@amt.cnet \
--to=mtosatti@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox