From: Anthony Liguori <anthony@codemonkey.ws>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
Michael Tokarev <mjt@tls.msk.ru>,
qemu-devel <qemu-devel@nongnu.org>,
Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] Reorganize and fix monitor resume after migration
Date: Fri, 05 Aug 2011 11:58:14 -0500 [thread overview]
Message-ID: <4E3C2126.207@redhat.com> (raw)
In-Reply-To: <4E3B979E.8030402@web.de>
On 08/05/2011 02:11 AM, Jan Kiszka wrote:
> From: Jan Kiszka<jan.kiszka@siemens.com>
>
> If migration failed in migrate_fd_put_buffer, the monitor may have been
> resumed not only in the error path of that function but also once again
> in migrate_fd_put_ready which is called unconditionally by
> migrate_fd_connect.
>
> Fix this by establishing a cleaner policy: the monitor shall be resumed
> when the migration file is closed, either via callback
> (migrate_fd_close) or in migrate_fd_cleanup if no file is open (i.e. no
> callback invoked).
>
> Signed-off-by: Jan Kiszka<jan.kiszka@siemens.com>
Applied. Thanks.
Regards,
Anthony Liguori
> ---
> migration.c | 19 +++++++++----------
> 1 files changed, 9 insertions(+), 10 deletions(-)
>
> diff --git a/migration.c b/migration.c
> index 2a15b98..756fa62 100644
> --- a/migration.c
> +++ b/migration.c
> @@ -292,18 +292,17 @@ int migrate_fd_cleanup(FdMigrationState *s)
> ret = -1;
> }
> s->file = NULL;
> + } else {
> + if (s->mon) {
> + monitor_resume(s->mon);
> + }
> }
>
> - if (s->fd != -1)
> + if (s->fd != -1) {
> close(s->fd);
> -
> - /* Don't resume monitor until we've flushed all of the buffers */
> - if (s->mon) {
> - monitor_resume(s->mon);
> + s->fd = -1;
> }
>
> - s->fd = -1;
> -
> return ret;
> }
>
> @@ -330,9 +329,6 @@ ssize_t migrate_fd_put_buffer(void *opaque, const void *data, size_t size)
> if (ret == -EAGAIN) {
> qemu_set_fd_handler2(s->fd, NULL, NULL, migrate_fd_put_notify, s);
> } else if (ret< 0) {
> - if (s->mon) {
> - monitor_resume(s->mon);
> - }
> s->state = MIG_STATE_ERROR;
> notifier_list_notify(&migration_state_notifiers, NULL);
> }
> @@ -458,6 +454,9 @@ int migrate_fd_close(void *opaque)
> {
> FdMigrationState *s = opaque;
>
> + if (s->mon) {
> + monitor_resume(s->mon);
> + }
> qemu_set_fd_handler2(s->fd, NULL, NULL, NULL, NULL);
> return s->close(s);
> }
prev parent reply other threads:[~2011-08-05 16:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-05 7:11 [Qemu-devel] [PATCH] Reorganize and fix monitor resume after migration Jan Kiszka
2011-08-05 7:28 ` Michael Tokarev
2011-08-05 16:58 ` Anthony Liguori [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=4E3C2126.207@redhat.com \
--to=anthony@codemonkey.ws \
--cc=jan.kiszka@web.de \
--cc=lcapitulino@redhat.com \
--cc=mjt@tls.msk.ru \
--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).