From: Paolo Bonzini <pbonzini@redhat.com>
To: "Radim Krčmář" <rkrcmar@redhat.com>,
"Marcelo Tosatti" <mtosatti@redhat.com>
Cc: kvm@vger.kernel.org, qemu-devel <qemu-devel@nongnu.org>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Juan Quintela <quintela@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>,
Roman Kagan <rkagan@virtuozzo.com>
Subject: Re: [QEMU PATCH] kvmclock: advance clock by time window between vm_stop and pre_save
Date: Fri, 4 Nov 2016 16:33:33 +0100 [thread overview]
Message-ID: <1c69a083-eef0-8fa0-0e74-5a4e25a066a0@redhat.com> (raw)
In-Reply-To: <20161104152522.GC5388@potion>
On 04/11/2016 16:25, Radim Krčmář wrote:
>> >
>> > + if (s->advance_clock && s->clock + s->advance_clock > s->clock) {
>> > + s->clock += s->advance_clock;
>> > + s->advance_clock = 0;
>> > + }
> Can't the advance_clock added to the migrated KVMClockState instead of
> passing it as another parameter?
>
> (It is sad that we can't just query KVMClockState in kvmclock_pre_save
> because of the Linux bug.)
What Linux bug? The one that makes us use kvmclock_current_nsec?
It should work with 4.9-rc (well, once Linus applies my pull request).
4.9-rc will not return ktime_get_ns for KVM_GET_CLOCK; it will return
the raw value from the kernel timekeeper.
I'm thinking that we should add a KVM capability for this, and skip
kvmclock_current_nsec if the capability is present. The first part is
trivial, so we can do it even during Linux rc period.
Paolo
next prev parent reply other threads:[~2016-11-04 15:33 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 9:43 [QEMU PATCH] kvmclock: advance clock by time window between vm_stop and pre_save Marcelo Tosatti
2016-11-04 12:28 ` Juan Quintela
2016-11-04 12:35 ` Marcelo Tosatti
2016-11-04 14:00 ` Marcelo Tosatti
2016-11-04 15:25 ` Radim Krčmář
2016-11-04 15:33 ` Paolo Bonzini [this message]
2016-11-04 15:48 ` Radim Krčmář
2016-11-04 15:57 ` Paolo Bonzini
2016-11-04 17:16 ` Radim Krčmář
2016-11-04 21:29 ` Paolo Bonzini
2016-11-04 21:47 ` Marcelo Tosatti
2016-11-04 22:35 ` Paolo Bonzini
2016-11-07 14:31 ` Roman Kagan
2016-11-07 19:31 ` Marcelo Tosatti
2016-11-04 16:24 ` Marcelo Tosatti
2016-11-04 17:34 ` Radim Krčmář
2016-11-04 18:29 ` Marcelo Tosatti
2016-11-04 20:07 ` Radim Krčmář
2016-11-04 16:04 ` Marcelo Tosatti
2016-11-04 17:07 ` Marcelo Tosatti
2016-11-04 17:39 ` Radim Krčmář
2016-11-04 18:31 ` Marcelo Tosatti
2016-11-07 13:08 ` Dr. David Alan Gilbert
2016-11-04 16:59 ` [QEMU PATCH v2] " Marcelo Tosatti
2016-11-04 18:57 ` Juan Quintela
2016-11-07 15:46 ` Dr. David Alan Gilbert
2016-11-07 19:41 ` Marcelo Tosatti
2016-11-07 20:03 ` Dr. David Alan Gilbert
2016-11-08 0:06 ` Marcelo Tosatti
2016-11-08 10:22 ` Dr. David Alan Gilbert
2016-11-08 13:32 ` Marcelo Tosatti
2016-11-09 19:32 ` Marcelo Tosatti
2016-11-09 16:23 ` Paolo Bonzini
2016-11-09 16:28 ` Dr. David Alan Gilbert
2016-11-09 16:33 ` Paolo Bonzini
2016-11-10 11:48 ` Marcelo Tosatti
2016-11-10 17:57 ` Paolo Bonzini
2016-11-11 14:23 ` Marcelo Tosatti
2017-02-07 10:02 ` Wanpeng Li
2017-02-07 12:18 ` 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=1c69a083-eef0-8fa0-0e74-5a4e25a066a0@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=rkagan@virtuozzo.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).