From: Paolo Bonzini <pbonzini@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>, kvm@vger.kernel.org
Cc: 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, 14 Nov 2016 14:54:38 +0100 [thread overview]
Message-ID: <a3e00c38-4d4d-d353-231d-9eb0233139e2@redhat.com> (raw)
In-Reply-To: <20161114123700.158592605@redhat.com>
On 14/11/2016 13:36, Marcelo Tosatti wrote:
> + /* 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()) {
> + time_at_migration = kvmclock_current_nsec(s);
Just assign to s->clock here...
> + }
> + /* migration/savevm/init restore */
> + } else {
> + /*
> + * use s->clock in case machine uses reliable
> + * get clock and host where vm was executing
> + * supported reliable get clock
> + */
> + if (!s->mach_use_reliable_get_clock ||
> + !s->src_use_reliable_get_clock) {
> + time_at_migration = kvmclock_current_nsec(s);
... and here, so that time_at_migration is not needed anymore.
Also here it's enough to look at s->src_user_reliable_get_clock, because
if s->mach_use_reliable_get_clock is false,
s->src_use_reliable_get_clock will be false as well.
> + }
> + }
>
> - /* We can't rely on the migrated clock value, just discard it */
> + /* We can't rely on the saved clock value, just discard it */
> if (time_at_migration) {
> s->clock = time_at_migration;
[...]
>
> +static bool kvmclock_src_use_reliable_get_clock(void *opaque)
> +{
> + KVMClockState *s = opaque;
> +
> + /*
> + * 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;
> + }
> +
> + return s->src_use_reliable_get_clock;
> +}
Here you can just return s->mach_use_reliable_get_clock. To set
s->src_use_reliable_get_clock, after issuing KVM_GET_CLOCK you can look
at the KVM_CLOCK_TSC_STABLE bit in the kvm_clock struct's flags.
You don't actually need kvm_has_adjust_clock_stable(), but please place
the KVM_GET_CLOCK code for kvmclock_pre_save and
kvmclock_vm_state_change in a common function.
Also, just another small nit: please make your scripts use the "-p"
option on diff. :)
Thanks,
Paolo
next prev parent reply other threads:[~2016-11-14 13:54 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 [this message]
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
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=a3e00c38-4d4d-d353-231d-9eb0233139e2@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).