From: Juan Quintela <quintela@redhat.com>
To: qemu-devel@nongnu.org
Cc: anthony@redhat.com
Subject: [Qemu-devel] [PULL 0/3] migration queue
Date: Fri, 12 Jul 2013 23:28:28 +0200 [thread overview]
Message-ID: <1373664508-5404-1-git-send-email-quintela@redhat.com> (raw)
Hi Anthony
please, pull.
This has Vinod changes for auto-converge.
I merged by hand the problems, and tested that it works and compiles
for everything.
Thanks, Juan.
PD: there were a prototype missing and the event name on trace-events,
fixed both.
The following changes since commit 25ca6a1f5a3ee0a1ae670590877ed14f05e28fba:
Merge remote-tracking branch 'agraf/ppc-for-upstream' into staging (2013-07-12 07:58:31 -0500)
are available in the git repository at:
git://github.com/juanquintela/qemu.git migration.next
for you to fetch changes up to 7ca1dfad952d8a8655b32e78623edcc38a51b14a:
Force auto-convegence of live migration (2013-07-12 20:35:08 +0200)
----------------------------------------------------------------
Chegu Vinod (3):
Introduce async_run_on_cpu()
Add 'auto-converge' migration capability
Force auto-convegence of live migration
arch_init.c | 81 +++++++++++++++++++++++++++++++++++++++++++
cpus.c | 29 ++++++++++++++++
include/migration/migration.h | 2 ++
include/qemu-common.h | 1 +
include/qom/cpu.h | 10 ++++++
migration.c | 9 +++++
qapi-schema.json | 2 +-
trace-events | 1 +
8 files changed, 134 insertions(+), 1 deletion(-)
next reply other threads:[~2013-07-12 21:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-12 21:28 Juan Quintela [this message]
2013-07-15 20:39 ` [Qemu-devel] [APPLIED] Merge remote-tracking branch 'quintela/migration.next' into staging Anthony Liguori
2013-07-15 20:42 ` Peter Maydell
2013-07-15 20:50 ` Anthony Liguori
-- strict thread matches above, loose matches on Subject: below --
2013-07-23 17:16 [Qemu-devel] [PULL 0/3] migration queue Juan Quintela
2017-08-02 13:58 Dr. David Alan Gilbert (git)
2017-08-02 14:50 ` Peter Maydell
2018-10-31 16:57 Dr. David Alan Gilbert (git)
2018-11-02 10:52 ` Peter Maydell
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=1373664508-5404-1-git-send-email-quintela@redhat.com \
--to=quintela@redhat.com \
--cc=anthony@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).