From: Wei Yang <richardw.yang@linux.intel.com>
To: qemu-devel@nongnu.org
Cc: Wei Yang <richardw.yang@linux.intel.com>,
dgilbert@redhat.com, quintela@redhat.com
Subject: [Qemu-devel] [PATCH 2/4] migration/ram.c: use same type in MultiFDPages_t to define offsest
Date: Tue, 28 May 2019 09:47:01 +0800 [thread overview]
Message-ID: <20190528014703.21030-3-richardw.yang@linux.intel.com> (raw)
In-Reply-To: <20190528014703.21030-1-richardw.yang@linux.intel.com>
MultiFDPacket_t.offset is allocated to store MultiFDPages_t.offset.
It would be better to use the same type.
Signed-off-by: Wei Yang <richardw.yang@linux.intel.com>
---
migration/ram.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/migration/ram.c b/migration/ram.c
index 4c60869226..dcf4c54eb5 100644
--- a/migration/ram.c
+++ b/migration/ram.c
@@ -607,7 +607,7 @@ typedef struct {
uint64_t packet_num;
uint64_t unused[4]; /* Reserved for future use */
char ramblock[256];
- uint64_t offset[];
+ ram_addr_t offset[];
} __attribute__((packed)) MultiFDPacket_t;
typedef struct {
--
2.19.1
next prev parent reply other threads:[~2019-05-28 1:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 1:46 [Qemu-devel] [PATCH 0/4] Multifd Cleanup Wei Yang
2019-05-28 1:47 ` [Qemu-devel] [PATCH 1/4] migration: multifd_save_setup always return 0 Wei Yang
2019-05-28 8:11 ` Juan Quintela
2019-05-29 0:34 ` Wei Yang
2019-05-29 8:22 ` Juan Quintela
2019-05-29 8:22 ` Juan Quintela
2019-05-28 1:47 ` Wei Yang [this message]
2019-05-28 8:12 ` [Qemu-devel] [PATCH 2/4] migration/ram.c: use same type in MultiFDPages_t to define offsest Juan Quintela
2019-05-29 0:34 ` Wei Yang
2019-05-28 1:47 ` [Qemu-devel] [PATCH 3/4] migration/ram.c: MultiFDSendParams.sem_sync is not really used Wei Yang
2019-05-28 8:16 ` Juan Quintela
2019-05-29 0:40 ` Wei Yang
2019-05-28 1:47 ` [Qemu-devel] [PATCH 4/4] migration/ram.c: multifd_send_state->count " Wei Yang
2019-05-28 8:19 ` Juan Quintela
2019-06-04 2:25 ` [Qemu-devel] [PATCH 0/4] Multifd Cleanup Wei Yang
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=20190528014703.21030-3-richardw.yang@linux.intel.com \
--to=richardw.yang@linux.intel.com \
--cc=dgilbert@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).