From: "Marcin Gibuła" <m.gibula@beyond.pl>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: pbonzini@redhat.com, Alexander Graf <agraf@suse.de>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] kvmclock: Ensure time in migration never goes backward
Date: Tue, 03 Jun 2014 11:11:52 +0200 [thread overview]
Message-ID: <538D9158.5070008@beyond.pl> (raw)
In-Reply-To: <20140603051630.GA2289@amt.cnet>
> Can you give this patch a try? Should read the guest TSC values after
> stopping the VM.
Yes, this patch fixes that.
Thanks,
--
mg
next prev parent reply other threads:[~2014-06-03 9:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 15:15 [PATCH v2] kvmclock: Ensure time in migration never goes backward Alexander Graf
2014-05-16 15:15 ` [Qemu-devel] " Alexander Graf
2014-05-18 13:20 ` Marcelo Tosatti
2014-05-18 13:20 ` [Qemu-devel] " Marcelo Tosatti
2014-05-19 11:31 ` Paolo Bonzini
2014-05-19 11:31 ` [Qemu-devel] " Paolo Bonzini
2014-05-21 10:03 ` Alexander Graf
2014-05-21 10:03 ` [Qemu-devel] " Alexander Graf
2014-06-02 20:31 ` Marcin Gibuła
2014-06-03 5:16 ` Marcelo Tosatti
2014-06-03 9:11 ` Marcin Gibuła [this message]
2014-06-03 11:13 ` Paolo Bonzini
2014-06-03 16:34 ` [Qemu-devel] [PATCH uq/master] kvmclock: Ensure proper env->tsc value for kvmclock_current_nsec calculation Marcelo Tosatti
2014-07-15 19:45 ` Paolo Bonzini
2014-07-15 20:03 ` Marcin Gibuła
2014-07-15 20:15 ` Paolo Bonzini
2014-07-15 20:31 ` Marcelo Tosatti
2014-07-15 20:34 ` Marcelo Tosatti
2014-07-15 20:43 ` Paolo Bonzini
2014-07-15 21:05 ` Andrey Korolyov
2014-07-15 21:08 ` Paolo Bonzini
2014-07-15 20:43 ` Paolo Bonzini
2014-07-15 19:44 ` [PATCH v2] kvmclock: Ensure time in migration never goes backward Paolo Bonzini
2014-07-15 19:44 ` [Qemu-devel] " Paolo Bonzini
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=538D9158.5070008@beyond.pl \
--to=m.gibula@beyond.pl \
--cc=agraf@suse.de \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.