From: Luiz Capitulino <lcapitulino@redhat.com>
To: Anthony Liguori <aliguori@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org, Juan Quintela <quintela@redhat.com>
Subject: [Qemu-devel] Re: [PATCH v3 0/5] Add QMP migration events
Date: Mon, 14 Jun 2010 11:24:14 -0300 [thread overview]
Message-ID: <20100614112414.1bead4ba@redhat.com> (raw)
In-Reply-To: <4C16357B.70308@linux.vnet.ibm.com>
On Mon, 14 Jun 2010 08:58:19 -0500
Anthony Liguori <aliguori@linux.vnet.ibm.com> wrote:
> For 0.13, we need to focus on introducing the least disruptive change
> that addresses the fundamental requirement--allow clients to avoid a
> polling loop for determining when migration ends. Having a single event
> with no payload is an extremely simple change.
Agreed.
Actually, I'm slightly against introducing the done event too. While the
polling is undesired, I don't think that having an event only for a release
is worth it.
next prev parent reply other threads:[~2010-06-14 14:24 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 12:10 [Qemu-devel] [PATCH v3 0/5] Add QMP migration events Juan Quintela
2010-06-09 12:10 ` [Qemu-devel] [PATCH v3 1/5] Exit if incoming migration fails Juan Quintela
2010-06-23 1:47 ` Anthony Liguori
2010-06-24 20:41 ` [Qemu-devel] [PATCH] win32: Add define for missing EPROTONOSUPPORT Stefan Weil
2010-06-27 20:25 ` Blue Swirl
2010-06-09 12:10 ` [Qemu-devel] [PATCH v3 2/5] Factorize common migration incoming code Juan Quintela
2010-06-09 12:10 ` [Qemu-devel] [PATCH v3 3/5] QMP: Introduce MIGRATION events Juan Quintela
2010-06-09 20:54 ` Luiz Capitulino
2010-06-10 10:33 ` [Qemu-devel] " Juan Quintela
2010-06-11 13:12 ` Luiz Capitulino
2010-06-09 12:10 ` [Qemu-devel] [PATCH v3 4/5] QMP: Emit migration events on incoming migration Juan Quintela
2010-06-09 12:10 ` [Qemu-devel] [PATCH v3 5/5] QMP: Emit migration events on outgoing migration Juan Quintela
2010-06-09 14:47 ` [Qemu-devel] [PATCH v3 0/5] Add QMP migration events Yoshiaki Tamura
2010-06-09 15:59 ` [Qemu-devel] " Juan Quintela
2010-06-09 22:07 ` Yoshiaki Tamura
2010-06-09 20:52 ` [Qemu-devel] " Luiz Capitulino
2010-06-09 21:19 ` Yoshiaki Tamura
2010-06-10 10:44 ` [Qemu-devel] " Juan Quintela
2010-06-11 14:30 ` Luiz Capitulino
2010-06-11 14:38 ` Anthony Liguori
2010-06-11 16:42 ` Luiz Capitulino
2010-06-12 11:20 ` Juan Quintela
2010-06-14 14:36 ` Luiz Capitulino
2010-06-14 15:45 ` Juan Quintela
2010-06-12 11:14 ` Juan Quintela
2010-06-14 13:58 ` Anthony Liguori
2010-06-14 14:24 ` Luiz Capitulino [this message]
2010-06-14 14:35 ` Anthony Liguori
2010-06-14 14:42 ` Luiz Capitulino
2010-06-12 11:05 ` Juan Quintela
2010-06-14 14:03 ` Anthony Liguori
2010-06-14 16:02 ` Juan Quintela
2010-06-14 16:10 ` Anthony Liguori
2010-06-14 18:35 ` Juan Quintela
2010-06-14 19:07 ` Anthony Liguori
2010-06-14 19:54 ` Juan Quintela
2010-06-14 20:01 ` Anthony Liguori
2010-06-15 10:30 ` Juan Quintela
2010-06-15 13:40 ` Luiz Capitulino
2010-06-15 15:24 ` Juan Quintela
2010-06-16 18:01 ` Luiz Capitulino
2010-06-16 19:10 ` Juan Quintela
2010-06-17 14:23 ` Luiz Capitulino
2010-06-17 16:34 ` Juan Quintela
2010-06-17 16:45 ` Luiz Capitulino
2010-06-17 17:53 ` Anthony Liguori
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=20100614112414.1bead4ba@redhat.com \
--to=lcapitulino@redhat.com \
--cc=aliguori@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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 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.