qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fabiano Rosas <farosas@suse.de>
To: qemu-devel@nongnu.org
Cc: "Daniel P . Berrangé" <berrange@redhat.com>,
	"Peter Xu" <peterx@redhat.com>
Subject: [PATCH v3 0/3] migration mapped-ram fixes
Date: Fri, 15 Mar 2024 00:20:37 -0300	[thread overview]
Message-ID: <20240315032040.7974-1-farosas@suse.de> (raw)

Hi,

In this v3:

patch 1 - The fd_is_socket() verification and an update to the comment
          in the code;

patch 2 - The fix for the fd-reuse bug in outgoing_args;

patch 3 - A proposal on how to fix the fd-socket vs. fd-file
          issue. I'm basically moving the fd_is_socket() call earlier
          to be able to do the checks properly.

based-on: https://gitlab.com/peterx/qemu/-/commits/migration-stable

CI run: https://gitlab.com/farosas/qemu/-/pipelines/1214405210

Fabiano Rosas (3):
  migration/multifd: Ensure we're not given a socket for file migration
  migration/multifd: Duplicate the fd for the outgoing_args
  migration: Add fd to FileMigrationArgs

 migration/fd.c        |  20 ++++++---
 migration/file.c      |   9 ++++
 migration/migration.c | 100 ++++++++++++++++++++++++++++++++++++------
 migration/migration.h |   1 +
 qapi/migration.json   |  11 ++++-
 5 files changed, 119 insertions(+), 22 deletions(-)

-- 
2.35.3



             reply	other threads:[~2024-03-15  3:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-15  3:20 Fabiano Rosas [this message]
2024-03-15  3:20 ` [PATCH v3 1/3] migration/multifd: Ensure we're not given a socket for file migration Fabiano Rosas
2024-03-15 11:38   ` Peter Xu
2024-03-15  3:20 ` [PATCH v3 2/3] migration/multifd: Duplicate the fd for the outgoing_args Fabiano Rosas
2024-03-15 11:39   ` Peter Xu
2024-03-15  3:20 ` [RFC PATCH v3 3/3] migration: Add fd to FileMigrationArgs Fabiano Rosas
2024-03-15  8:55   ` Daniel P. Berrangé
2024-03-15 12:13     ` Fabiano Rosas
2024-03-19 16:31       ` Daniel P. Berrangé
2024-03-15 16:05     ` Peter Xu
2024-03-15 18:01       ` Fabiano Rosas
2024-03-15 20:54         ` Peter Xu
2024-03-19 16:25           ` Daniel P. Berrangé
2024-03-19 19:25             ` Peter Xu
2024-03-19 19:52               ` Daniel P. Berrangé
2024-03-19 20:15                 ` Peter Xu

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=20240315032040.7974-1-farosas@suse.de \
    --to=farosas@suse.de \
    --cc=berrange@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).