From: Juan Quintela <quintela@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Juan Quintela" <quintela@redhat.com>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
"Yanan Wang" <wangyanan55@huawei.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Eduardo Habkost" <eduardo@habkost.net>,
"Eric Blake" <eblake@redhat.com>
Subject: [PATCH v3 6/6] ram: Document migration ram flags
Date: Wed, 8 Feb 2023 14:30:10 +0100 [thread overview]
Message-ID: <20230208133010.17323-7-quintela@redhat.com> (raw)
In-Reply-To: <20230208133010.17323-1-quintela@redhat.com>
0x80 is RAM_SAVE_FLAG_HOOK, it is in qemu-file now.
Bigger usable flag is 0x200, noticing that.
We can reuse RAM_SAVE_FLAG_FULL.
Signed-off-by: Juan Quintela <quintela@redhat.com>
---
migration/ram.c | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/migration/ram.c b/migration/ram.c
index 7952d5f01c..d95e26c03c 100644
--- a/migration/ram.c
+++ b/migration/ram.c
@@ -73,16 +73,19 @@
* RAM_SSAVE_FLAG_COMPRESS_PAGE just rename it.
*/
-#define RAM_SAVE_FLAG_FULL 0x01 /* Obsolete, not used anymore */
+/* RAM_SAVE_FLAG_FULL has been obsoleted since at least 2009, we can
+ * reuse it */
+#define RAM_SAVE_FLAG_FULL 0x01
#define RAM_SAVE_FLAG_ZERO 0x02
#define RAM_SAVE_FLAG_MEM_SIZE 0x04
#define RAM_SAVE_FLAG_PAGE 0x08
#define RAM_SAVE_FLAG_EOS 0x10
#define RAM_SAVE_FLAG_CONTINUE 0x20
#define RAM_SAVE_FLAG_XBZRLE 0x40
-/* 0x80 is reserved in migration.h start with 0x100 next */
+/* 0x80 is reserved in qemu-file.h for RAM_SAVE_FLAG_HOOK */
#define RAM_SAVE_FLAG_COMPRESS_PAGE 0x100
#define RAM_SAVE_FLAG_MULTIFD_SYNC 0x200
+/* We can't use any flag that is bigger that 0x200 */
XBZRLECacheStats xbzrle_counters;
--
2.39.1
next prev parent reply other threads:[~2023-02-08 13:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 13:30 [PATCH v3 0/6] Eliminate multifd flush Juan Quintela
2023-02-08 13:30 ` [PATCH v3 1/6] multifd: Create property multifd-sync-after-each-section Juan Quintela
[not found] ` <20230208202526.p2jmikndw5lx2ong@redhat.com>
2023-02-09 13:22 ` Juan Quintela
2023-02-08 13:30 ` [PATCH v3 2/6] multifd: Protect multifd_send_sync_main() calls Juan Quintela
2023-02-08 13:30 ` [PATCH v3 3/6] migration: Simplify ram_find_and_save_block() Juan Quintela
2023-02-08 13:30 ` [PATCH v3 4/6] migration: Make find_dirty_block() return a single parameter Juan Quintela
2023-02-08 13:30 ` [PATCH v3 5/6] multifd: Only sync once each full round of memory Juan Quintela
2023-02-08 13:30 ` Juan Quintela [this message]
2023-02-08 20:29 ` [PATCH v3 6/6] ram: Document migration ram flags Eric Blake
2023-02-09 13:27 ` 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=20230208133010.17323-7-quintela@redhat.com \
--to=quintela@redhat.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=eduardo@habkost.net \
--cc=marcel.apfelbaum@gmail.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=wangyanan55@huawei.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).