From: Peter Xu <peterx@redhat.com>
To: Juan Quintela <quintela@redhat.com>
Cc: qemu-devel@nongnu.org, "Fabiano Rosas" <farosas@suse.de>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Xiaohui Li" <xiaohli@redhat.com>
Subject: Re: [PATCH v4 2/5] migration: Allow network to fail even during recovery
Date: Tue, 31 Oct 2023 11:32:56 -0400 [thread overview]
Message-ID: <ZUEeKDXMuSKaGY7q@x1n> (raw)
In-Reply-To: <87il6m7tr1.fsf@secure.mitica>
On Tue, Oct 31, 2023 at 03:26:42PM +0100, Juan Quintela wrote:
> > -void migration_rp_wait(MigrationState *s)
> > +int migration_rp_wait(MigrationState *s)
> > {
> > + /* If migration has failure already, ignore the wait */
> > + if (migrate_has_error(s)) {
> > + return -1;
> > + }
> > +
> > qemu_sem_wait(&s->rp_state.rp_sem);
> > +
> > + /* After wait, double check that there's no failure */
> > + if (migrate_has_error(s)) {
> > + return -1;
> > + }
> > +
> > + return 0;
> > }
>
> Shouldn't this be bool?
>
> We have (too many) functions in migration that returns 0/-1 and set an
> error, I think we should change them to return bool. Or even just test
> if err is set.
Yeah this patch comes earlier than "switching to bools". I can make them
bool after I rebase to the new pulls and see what's leftover. Thanks.
--
Peter Xu
next prev parent reply other threads:[~2023-10-31 15:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 20:26 [PATCH v4 0/5] migration: Better error handling in rp thread, allow failures in recover Peter Xu
2023-10-17 20:26 ` [PATCH v4 1/5] migration: Refactor error handling in source return path Peter Xu
2023-10-19 21:09 ` Fabiano Rosas
2023-10-31 13:47 ` Juan Quintela
2023-10-17 20:26 ` [PATCH v4 2/5] migration: Allow network to fail even during recovery Peter Xu
2023-10-31 14:26 ` Juan Quintela
2023-10-31 15:32 ` Peter Xu [this message]
2023-10-17 20:26 ` [PATCH v4 3/5] tests/migration-test: Add a test for postcopy hangs during RECOVER Peter Xu
2023-10-31 22:01 ` Fabiano Rosas
2023-10-31 22:19 ` Peter Xu
2023-10-31 22:34 ` Juan Quintela
2023-10-17 20:26 ` [PATCH v4 4/5] migration: Change ram_dirty_bitmap_reload() retval to bool Peter Xu
2023-10-19 21:12 ` Fabiano Rosas
2023-10-31 14:30 ` Juan Quintela
2023-10-17 20:26 ` [PATCH v4 5/5] migration: Change ram_save_queue_pages() " Peter Xu
2023-10-19 21:13 ` Fabiano Rosas
2023-10-31 14:34 ` 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=ZUEeKDXMuSKaGY7q@x1n \
--to=peterx@redhat.com \
--cc=farosas@suse.de \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=xiaohli@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).