From: Paolo Bonzini <pbonzini@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>, qemu-devel@nongnu.org
Cc: "Andrey Korolyov" <andrey@xdel.ru>, "Marcin Gibuła" <m.gibula@beyond.pl>
Subject: Re: [Qemu-devel] [patch 0/3] kvmclock: Ensure time in migration never goes backward (v3)
Date: Tue, 16 Sep 2014 11:14:21 +0200 [thread overview]
Message-ID: <5417FF6D.8020009@redhat.com> (raw)
In-Reply-To: <20140905135244.104423770@amt.cnet>
Il 05/09/2014 15:52, Marcelo Tosatti ha scritto:
> Regression fix tested with fio and ping-pong migration.
I applied the patches, but in a different order (2-3-1) to keep them
bisectable.
Can you send a follow-up patch, adding a comment before the call to
cpu_clean_all_dirty that explains what's going on?
Paolo
prev parent reply other threads:[~2014-09-16 9:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-05 13:52 [Qemu-devel] [patch 0/3] kvmclock: Ensure time in migration never goes backward (v3) Marcelo Tosatti
2014-09-05 13:52 ` [Qemu-devel] [patch 1/3] kvmclock: Ensure time in migration never goes backward Marcelo Tosatti
2014-09-09 15:12 ` Marcelo Tosatti
2014-09-09 21:16 ` Alexander Graf
2014-09-09 23:07 ` Marcelo Tosatti
2014-09-05 13:52 ` [Qemu-devel] [patch 2/3] Introduce cpu_clean_all_dirty Marcelo Tosatti
2014-09-05 13:52 ` [Qemu-devel] [patch 3/3] kvmclock: Ensure proper env->tsc value for kvmclock_current_nsec calculation Marcelo Tosatti
2014-09-05 18:16 ` [Qemu-devel] [patch 0/3] kvmclock: Ensure time in migration never goes backward (v3) Andrey Korolyov
2014-09-05 18:26 ` Marcelo Tosatti
2014-09-05 18:29 ` Paolo Bonzini
2014-09-05 18:35 ` Andrey Korolyov
2014-09-05 19:35 ` Andrey Korolyov
2014-09-05 22:14 ` Paolo Bonzini
2014-09-05 23:05 ` Andrey Korolyov
2014-09-09 17:54 ` Andrey Korolyov
2014-09-16 9:14 ` Paolo Bonzini [this message]
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=5417FF6D.8020009@redhat.com \
--to=pbonzini@redhat.com \
--cc=andrey@xdel.ru \
--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).