From: Paolo Bonzini <pbonzini@redhat.com>
To: "Marcin Gibuła" <m.gibula@beyond.pl>,
"Marcelo Tosatti" <mtosatti@redhat.com>
Cc: Alexander Graf <agraf@suse.de>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH uq/master] kvmclock: Ensure proper env->tsc value for kvmclock_current_nsec calculation
Date: Tue, 15 Jul 2014 22:15:14 +0200 [thread overview]
Message-ID: <53C58BD2.602@redhat.com> (raw)
In-Reply-To: <53C588F4.4040307@beyond.pl>
Il 15/07/2014 22:03, Marcin Gibuła ha scritto:
>> This causes a hang during migration, so I'll revert the patch from 2.1.
>
> For me this patch series fixed all hangs I had with migration (at least
> with qemu 2.0).
Unfortunately, someone else bisected their hangs exactly to this patch:
http://permalink.gmane.org/gmane.comp.emulators.qemu/286681
I could not reproduce that, but I couldn't reproduce yours either so I'm
inclined to trust him and revert the patch.
Paolo
next prev parent reply other threads:[~2014-07-15 20:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 15:15 [Qemu-devel] [PATCH v2] kvmclock: Ensure time in migration never goes backward Alexander Graf
2014-05-18 13:20 ` Marcelo Tosatti
2014-05-19 11:31 ` Paolo Bonzini
2014-05-21 10:03 ` 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
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 [this message]
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 ` [Qemu-devel] [PATCH v2] kvmclock: Ensure time in migration never goes backward 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=53C58BD2.602@redhat.com \
--to=pbonzini@redhat.com \
--cc=agraf@suse.de \
--cc=m.gibula@beyond.pl \
--cc=mtosatti@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 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).