qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Prasad Pandit <ppandit@redhat.com>
To: qemu-devel@nongnu.org
Cc: peterx@redhat.com, farosas@suse.de, berrange@redhat.com,
	Prasad Pandit <pjp@fedoraproject.org>
Subject: [PATCH v6 1/4] migration/multifd: move macros to multifd header
Date: Sat, 15 Feb 2025 18:01:16 +0530	[thread overview]
Message-ID: <20250215123119.814345-2-ppandit@redhat.com> (raw)
In-Reply-To: <20250215123119.814345-1-ppandit@redhat.com>

From: Prasad Pandit <pjp@fedoraproject.org>

Move MULTIFD_ macros to the header file so that
they are accessible from other source files.

Reviewed-by: Fabiano Rosas <farosas@suse.de>
Signed-off-by: Prasad Pandit <pjp@fedoraproject.org>
---
 migration/multifd.c | 5 -----
 migration/multifd.h | 5 +++++
 2 files changed, 5 insertions(+), 5 deletions(-)

v5: no change
- https://lore.kernel.org/qemu-devel/20250205122712.229151-1-ppandit@redhat.com/T/#t

diff --git a/migration/multifd.c b/migration/multifd.c
index ab73d6d984..97ce831775 100644
--- a/migration/multifd.c
+++ b/migration/multifd.c
@@ -33,11 +33,6 @@
 #include "io/channel-socket.h"
 #include "yank_functions.h"
 
-/* Multiple fd's */
-
-#define MULTIFD_MAGIC 0x11223344U
-#define MULTIFD_VERSION 1
-
 typedef struct {
     uint32_t magic;
     uint32_t version;
diff --git a/migration/multifd.h b/migration/multifd.h
index bd785b9873..10149af654 100644
--- a/migration/multifd.h
+++ b/migration/multifd.h
@@ -49,6 +49,11 @@ bool multifd_queue_page(RAMBlock *block, ram_addr_t offset);
 bool multifd_recv(void);
 MultiFDRecvData *multifd_get_recv_data(void);
 
+/* Multiple fd's */
+
+#define MULTIFD_MAGIC 0x11223344U
+#define MULTIFD_VERSION 1
+
 /* Multifd Compression flags */
 #define MULTIFD_FLAG_SYNC (1 << 0)
 
--
2.48.1



  reply	other threads:[~2025-02-15 12:32 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-15 12:31 [PATCH v6 0/4] Allow to enable multifd and postcopy migration together Prasad Pandit
2025-02-15 12:31 ` Prasad Pandit [this message]
2025-02-15 12:31 ` [PATCH v6 2/4] migration: enable multifd and postcopy together Prasad Pandit
2025-02-17 21:49   ` Fabiano Rosas
2025-02-18  8:17     ` Prasad Pandit
2025-02-18 14:22       ` Fabiano Rosas
2025-02-19 11:57         ` Prasad Pandit
2025-02-19 17:22           ` Fabiano Rosas
2025-02-20  9:47             ` Prasad Pandit
2025-02-20 13:36               ` Fabiano Rosas
2025-02-21  8:44                 ` Prasad Pandit
2025-02-18 11:17   ` Juraj Marcin
2025-02-19  7:13     ` Prasad Pandit
2025-02-15 12:31 ` [PATCH v6 3/4] tests/qtest/migration: consolidate set capabilities Prasad Pandit
2025-02-17 15:17   ` Fabiano Rosas
2025-02-18  8:53     ` Prasad Pandit
2025-02-15 12:31 ` [PATCH v6 4/4] tests/qtest/migration: add postcopy tests with multifd Prasad Pandit
2025-02-17 15:33   ` Fabiano Rosas
2025-02-18  8:58     ` Prasad Pandit
2025-02-18 14:28       ` Fabiano Rosas
2025-02-25  7:25         ` Prasad Pandit
2025-02-25 13:07           ` Fabiano Rosas

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=20250215123119.814345-2-ppandit@redhat.com \
    --to=ppandit@redhat.com \
    --cc=berrange@redhat.com \
    --cc=farosas@suse.de \
    --cc=peterx@redhat.com \
    --cc=pjp@fedoraproject.org \
    --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).