From: Juan Quintela <quintela@redhat.com>
To: qemu-devel@nongnu.org
Cc: dgilbert@redhat.com, lvivier@redhat.com, peterx@redhat.com
Subject: [Qemu-devel] [PATCH v15 11/12] migration: Remove not needed semaphore and quit
Date: Thu, 21 Jun 2018 01:28:50 +0200 [thread overview]
Message-ID: <20180620232851.7152-12-quintela@redhat.com> (raw)
In-Reply-To: <20180620232851.7152-1-quintela@redhat.com>
We know quit closing the QIO.
Signed-off-by: Juan Quintela <quintela@redhat.com>
--
Add comment
don't object_ref() twice.
---
migration/ram.c | 17 ++++++-----------
1 file changed, 6 insertions(+), 11 deletions(-)
diff --git a/migration/ram.c b/migration/ram.c
index 2c3a452a7d..57d3ad1c45 100644
--- a/migration/ram.c
+++ b/migration/ram.c
@@ -594,14 +594,10 @@ typedef struct {
QemuThread thread;
/* communication channel */
QIOChannel *c;
- /* sem where to wait for more work */
- QemuSemaphore sem;
/* this mutex protects the following parameters */
QemuMutex mutex;
/* is this channel thread running */
bool running;
- /* should this thread finish */
- bool quit;
/* array of pages to receive */
MultiFDPages_t *pages;
/* packet allocated len */
@@ -1152,8 +1148,12 @@ static void multifd_recv_terminate_threads(Error *err)
MultiFDRecvParams *p = &multifd_recv_state->params[i];
qemu_mutex_lock(&p->mutex);
- p->quit = true;
- qemu_sem_post(&p->sem);
+ /* We could arrive here for two reasons:
+ - normal quit, i.e. everything went fine, just finished
+ - error quit: We close the channels so the channel threads
+ finish the qio_channel_read_all_eof() */
+ object_unref(OBJECT(p->c));
+ p->c = NULL;
qemu_mutex_unlock(&p->mutex);
}
}
@@ -1173,10 +1173,7 @@ int multifd_load_cleanup(Error **errp)
if (p->running) {
qemu_thread_join(&p->thread);
}
- object_unref(OBJECT(p->c));
- p->c = NULL;
qemu_mutex_destroy(&p->mutex);
- qemu_sem_destroy(&p->sem);
qemu_sem_destroy(&p->sem_sync);
g_free(p->name);
p->name = NULL;
@@ -1299,9 +1296,7 @@ int multifd_load_setup(void)
MultiFDRecvParams *p = &multifd_recv_state->params[i];
qemu_mutex_init(&p->mutex);
- qemu_sem_init(&p->sem, 0);
qemu_sem_init(&p->sem_sync, 0);
- p->quit = false;
p->id = i;
p->pages = multifd_pages_init(page_count);
p->packet_len = sizeof(MultiFDPacket_t)
--
2.17.1
next prev parent reply other threads:[~2018-06-20 23:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-20 23:28 [Qemu-devel] [PATCH v15 00/12] Multifd Juan Quintela
2018-06-20 23:28 ` [Qemu-devel] [PATCH v15 01/12] migration: Create multipage support Juan Quintela
2018-06-20 23:28 ` [Qemu-devel] [PATCH v15 02/12] migration: Create multifd packet Juan Quintela
2018-06-20 23:28 ` [Qemu-devel] [PATCH v15 03/12] migration: Add multifd traces for start/end thread Juan Quintela
2018-06-20 23:28 ` [Qemu-devel] [PATCH v15 04/12] migration: Calculate transferred ram correctly Juan Quintela
2018-06-20 23:28 ` [Qemu-devel] [PATCH v15 05/12] migration: Multifd channels always wait on the sem Juan Quintela
2018-06-20 23:28 ` [Qemu-devel] [PATCH v15 06/12] migration: Add block where to send/receive packets Juan Quintela
2018-06-20 23:28 ` [Qemu-devel] [PATCH v15 07/12] migration: Synchronize multifd threads with main thread Juan Quintela
2018-06-21 9:57 ` Dr. David Alan Gilbert
2018-06-20 23:28 ` [Qemu-devel] [PATCH v15 08/12] migration: Create ram_save_multifd_page Juan Quintela
2018-06-20 23:28 ` [Qemu-devel] [PATCH v15 09/12] migration: Start sending messages Juan Quintela
2018-06-20 23:28 ` [Qemu-devel] [PATCH v15 10/12] migration: Wait for blocking IO Juan Quintela
2018-06-20 23:28 ` Juan Quintela [this message]
2018-06-20 23:28 ` [Qemu-devel] [PATCH v15 12/12] migration: Stop sending whole pages through main channel Juan Quintela
2018-06-21 1:08 ` [Qemu-devel] [PATCH v15 00/12] Multifd no-reply
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=20180620232851.7152-12-quintela@redhat.com \
--to=quintela@redhat.com \
--cc=dgilbert@redhat.com \
--cc=lvivier@redhat.com \
--cc=peterx@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).