From: Fabiano Rosas <farosas@suse.de>
To: qemu-devel@nongnu.org
Cc: Juan Quintela <quintela@redhat.com>, Peter Xu <peterx@redhat.com>
Subject: [PATCH 0/3] migration/multifd: General cleanups
Date: Thu, 12 Oct 2023 10:43:40 -0300 [thread overview]
Message-ID: <20231012134343.23757-1-farosas@suse.de> (raw)
Hi,
Just a small series with some cleanups.
First patch is related to fixed ram work. If we're going to add other
transports to multifd such as the "file", we need to stop using
"socket" in the code.
Second patch is a consolidation of error paths that I think will make
the code more robust.
Third patch is a refactoring to improve Error handling. We're
currently doing some gymnastics that are not necessary.
Thanks!
Fabiano Rosas (3):
migration/multifd: Remove direct "socket" references
migration/multifd: Unify multifd_send_thread error paths
migration/multifd: Clarify Error usage in multifd_channel_connect
migration/multifd.c | 92 +++++++++++++++++++++---------------------
migration/trace-events | 3 +-
2 files changed, 48 insertions(+), 47 deletions(-)
--
2.35.3
next reply other threads:[~2023-10-12 13:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 13:43 Fabiano Rosas [this message]
2023-10-12 13:43 ` [PATCH 1/3] migration/multifd: Remove direct "socket" references Fabiano Rosas
2023-10-12 13:53 ` Philippe Mathieu-Daudé
2023-10-16 8:45 ` Juan Quintela
2023-10-12 13:43 ` [PATCH 2/3] migration/multifd: Unify multifd_send_thread error paths Fabiano Rosas
2023-10-16 8:48 ` Juan Quintela
2023-10-12 13:43 ` [PATCH 3/3] migration/multifd: Clarify Error usage in multifd_channel_connect Fabiano Rosas
2023-10-12 13:53 ` Philippe Mathieu-Daudé
2023-10-16 8:50 ` 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=20231012134343.23757-1-farosas@suse.de \
--to=farosas@suse.de \
--cc=peterx@redhat.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 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).