From: Paolo Bonzini <pbonzini@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Juan Quintela <quintela@redhat.com>,
Radim Krcmar <rkrcmar@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: [qemu patch 2/2] kvmclock: reduce kvmclock difference on migration
Date: Mon, 28 Nov 2016 14:47:18 +0100 [thread overview]
Message-ID: <1023a283-77a7-45e5-8877-6264e08d0658@redhat.com> (raw)
In-Reply-To: <20161117121637.GA13404@amt.cnet>
On 17/11/2016 13:16, Marcelo Tosatti wrote:
> What QEMU wants is to use KVM_GET_CLOCK at pre_save independently
> of whether masterclock is enabled or not... it just depends
> on KVM_GET_CLOCK being correct for the masterclock case
> (108b249c453dd7132599ab6dc7e435a7036c193f).
>
> So a "reliable KVM_GET_CLOCK" (that does not timebackward
> when masterclock is enabled) is much simpler to userspace
> than "whether masterclock is enabled or not".
>
> If you have a reason why that should not be the case,
> let me know.
I still cannot understand this case.
If the source has masterclock _disabled_, shouldn't it read kvmclock
from memory? But that's not what your patch does. To be clear, what
I mean is:
diff --git a/hw/i386/kvm/clock.c b/hw/i386/kvm/clock.c
index 653b0b4..6f6e2dc 100644
--- a/hw/i386/kvm/clock.c
+++ b/hw/i386/kvm/clock.c
@@ -97,6 +97,7 @@ static uint64_t kvm_get_clock(void)
fprintf(stderr, "KVM_GET_CLOCK failed: %s\n", strerror(ret));
abort();
}
+ s->src_use_reliable_get_clock = data.flags & KVM_CLOCK_TSC_STABLE;
return data.clock;
}
@@ -110,34 +111,19 @@ static void kvmclock_vm_state_change(void *opaque, int running,
if (running) {
struct kvm_clock_data data = {};
- uint64_t pvclock_via_mem = 0;
- /* local (running VM) restore */
- if (s->clock_valid) {
- /*
- * if host does not support reliable KVM_GET_CLOCK,
- * read kvmclock value from memory
- */
- if (!kvm_has_adjust_clock_stable()) {
- pvclock_via_mem = kvmclock_current_nsec(s);
- }
- /* migration/savevm/init restore */
- } else {
- /*
- * use s->clock in case machine uses reliable
- * get clock and source host supported
- * reliable get clock
- */
- if (!s->src_use_reliable_get_clock) {
- pvclock_via_mem = kvmclock_current_nsec(s);
+ /*
+ * if last KVM_GET_CLOCK did not retrieve a reliable value,
+ * we can't rely on the saved clock value. Just discard it and
+ * read kvmclock value from memory
+ */
+ if (!s->src_use_reliable_get_clock) {
+ uint64_t pvclock_via_mem = kvmclock_current_nsec(s);
+ if (pvclock_via_mem) {
+ s->clock = pvclock_via_mem;
}
}
- /* We can't rely on the saved clock value, just discard it */
- if (pvclock_via_mem) {
- s->clock = pvclock_via_mem;
- }
-
s->clock_valid = false;
data.clock = s->clock;
@@ -181,16 +168,6 @@ static void kvmclock_realize(DeviceState *dev, Error **errp)
{
KVMClockState *s = KVM_CLOCK(dev);
- /*
- * On machine types that support reliable KVM_GET_CLOCK,
- * if host kernel does provide reliable KVM_GET_CLOCK,
- * set src_use_reliable_get_clock=true so that destination
- * avoids reading kvmclock from memory.
- */
- if (s->mach_use_reliable_get_clock && kvm_has_adjust_clock_stable()) {
- s->src_use_reliable_get_clock = true;
- }
-
qemu_add_vm_change_state_handler(kvmclock_vm_state_change, s);
}
next prev parent reply other threads:[~2016-11-28 13:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 12:36 [qemu patch 0/2] improve kvmclock difference on migration Marcelo Tosatti
2016-11-14 12:36 ` [qemu patch 1/2] kvm: sync linux headers Marcelo Tosatti
2016-11-14 12:36 ` [qemu patch 2/2] kvmclock: reduce kvmclock difference on migration Marcelo Tosatti
2016-11-14 13:54 ` Paolo Bonzini
2016-11-14 14:00 ` Marcelo Tosatti
2016-11-14 14:22 ` Paolo Bonzini
2016-11-14 14:50 ` Marcelo Tosatti
2016-11-14 15:00 ` Paolo Bonzini
2016-11-14 15:40 ` Marcelo Tosatti
2016-11-14 16:43 ` Paolo Bonzini
2016-11-14 17:13 ` Marcelo Tosatti
2016-11-14 17:20 ` Paolo Bonzini
2016-11-14 18:15 ` Marcelo Tosatti
2016-11-17 12:16 ` Marcelo Tosatti
2016-11-17 13:03 ` Paolo Bonzini
2016-11-28 13:47 ` Paolo Bonzini [this message]
2016-11-28 14:28 ` Eduardo Habkost
2016-11-28 15:12 ` Paolo Bonzini
2016-11-28 16:36 ` Marcelo Tosatti
2016-11-28 17:30 ` Paolo Bonzini
2016-11-14 14:11 ` Juan Quintela
2016-11-14 14:09 ` Juan Quintela
2016-11-14 15:37 ` 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=1023a283-77a7-45e5-8877-6264e08d0658@redhat.com \
--to=pbonzini@redhat.com \
--cc=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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;
as well as URLs for NNTP newsgroup(s).