From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Juan Quintela <quintela@redhat.com>
Cc: Laurent Vivier <lvivier@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Thomas Huth <thuth@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH v2 2/3] migration: Make sure that we don't call write() in case of error
Date: Tue, 7 Jan 2020 11:21:33 +0000 [thread overview]
Message-ID: <20200107112133.GC2732@work-vm> (raw)
In-Reply-To: <20200107104914.1814-3-quintela@redhat.com>
* Juan Quintela (quintela@redhat.com) wrote:
> If we are exiting due to an error/finish/.... Just don't try to even
> touch the channel with one IO operation.
>
> Signed-off-by: Juan Quintela <quintela@redhat.com>
> Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> Signed-off-by: Juan Quintela <quintela@redhat.com>
> ---
> migration/ram.c | 25 +++++++++++++++++++++++++
> 1 file changed, 25 insertions(+)
>
> diff --git a/migration/ram.c b/migration/ram.c
> index 96feb4062c..6e678dbd2e 100644
> --- a/migration/ram.c
> +++ b/migration/ram.c
> @@ -900,6 +900,12 @@ struct {
> uint64_t packet_num;
> /* send channels ready */
> QemuSemaphore channels_ready;
> + /*
> + * Have we already run terminate threads. There is a race when it
> + * happens that we got one error while we are exiting.
> + * We will use atomic operations. Only valid values are 0 and 1.
> + */
> + int exiting;
> } *multifd_send_state;
>
> /*
> @@ -928,6 +934,10 @@ static int multifd_send_pages(RAMState *rs)
> MultiFDPages_t *pages = multifd_send_state->pages;
> uint64_t transferred;
>
> + if (atomic_read(&multifd_send_state->exiting)) {
> + return -1;
> + }
> +
> qemu_sem_wait(&multifd_send_state->channels_ready);
> for (i = next_channel;; i = (i + 1) % migrate_multifd_channels()) {
> p = &multifd_send_state->params[i];
> @@ -1009,6 +1019,16 @@ static void multifd_send_terminate_threads(Error *err)
> }
> }
>
> + /*
> + * We don't want to exit each threads twice. Depending on where
> + * we get the error, or if there are two independent errors in two
> + * threads at the same time, we can end calling this function
> + * twice.
> + */
Yeh that makes it cleaer. Thanks
> + if (atomic_xchg(&multifd_send_state->exiting, 1)) {
> + return;
> + }
> +
> for (i = 0; i < migrate_multifd_channels(); i++) {
> MultiFDSendParams *p = &multifd_send_state->params[i];
>
> @@ -1118,6 +1138,10 @@ static void *multifd_send_thread(void *opaque)
>
> while (true) {
> qemu_sem_wait(&p->sem);
> +
> + if (atomic_read(&multifd_send_state->exiting)) {
> + break;
> + }
> qemu_mutex_lock(&p->mutex);
>
> if (p->pending_job) {
> @@ -1224,6 +1248,7 @@ int multifd_save_setup(void)
> multifd_send_state->params = g_new0(MultiFDSendParams, thread_count);
> multifd_send_state->pages = multifd_pages_init(page_count);
> qemu_sem_init(&multifd_send_state->channels_ready, 0);
> + atomic_set(&multifd_send_state->exiting, 0);
>
> for (i = 0; i < thread_count; i++) {
> MultiFDSendParams *p = &multifd_send_state->params[i];
> --
> 2.24.1
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2020-01-07 11:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 10:49 [PATCH v2 0/3] Fix multifd + cancel + multifd Juan Quintela
2020-01-07 10:49 ` [PATCH v2 1/3] migration-test: Add migration multifd test Juan Quintela
2020-01-07 11:07 ` Dr. David Alan Gilbert
2020-01-07 11:56 ` Juan Quintela
2020-01-07 10:49 ` [PATCH v2 2/3] migration: Make sure that we don't call write() in case of error Juan Quintela
2020-01-07 11:21 ` Dr. David Alan Gilbert [this message]
2020-01-07 10:49 ` [PATCH v2 3/3] migration-test: Make sure that multifd and cancel works Juan Quintela
2020-01-07 11:27 ` Dr. David Alan Gilbert
2020-01-07 11:46 ` Juan Quintela
2020-01-07 11:49 ` Dr. David Alan Gilbert
2020-01-07 12:07 ` [PATCH v2 0/3] Fix multifd + cancel + multifd no-reply
2020-01-07 15:39 ` Juan Quintela
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=20200107112133.GC2732@work-vm \
--to=dgilbert@redhat.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=thuth@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 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).