From: "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>
To: qemu-devel@nongnu.org
Cc: amit.shah@redhat.com, quintela@redhat.com
Subject: [Qemu-devel] [PATCH] RDMA: Reduce restriction on block length match
Date: Wed, 8 Jul 2015 15:26:07 +0100 [thread overview]
Message-ID: <1436365567-27164-1-git-send-email-dgilbert@redhat.com> (raw)
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
My e4d633207 patch has an over zealous sanity check that checked
the lengths of the RAM Blocks on source/destination were the same. This
isn't true because of the 'used_length' trick for RAM blocks like the
ACPI table that vary in size.
Prior to that patch RDMA would also fail in this case, but it should
now work with the changes in the set e4d633207 is in.
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Fixes: e4d633207c129dc5b7d145240ac4a1997ef3902f
---
migration/rdma.c | 13 +++++++------
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/migration/rdma.c b/migration/rdma.c
index f106b2a..1d094b0 100644
--- a/migration/rdma.c
+++ b/migration/rdma.c
@@ -3338,14 +3338,15 @@ static int qemu_rdma_registration_stop(QEMUFile *f, void *opaque,
for (i = 0; i < nb_dest_blocks; i++) {
network_to_dest_block(&rdma->dest_blocks[i]);
- /* We require that the blocks are in the same order */
+ /* We require that the blocks are in the same order,
+ * but the used_length trick for acpi blocks means that
+ * the destination can validly be larger than the source
+ */
if (rdma->dest_blocks[i].length != local->block[i].length) {
- ERROR(errp, "Block %s/%d has a different length %" PRIu64
- "vs %" PRIu64, local->block[i].block_name, i,
- local->block[i].length,
+ fprintf(stderr, "INFO: Block %s/%d has a different length %"
+ PRIu64 "vs %" PRIu64, local->block[i].block_name,
+ i, local->block[i].length,
rdma->dest_blocks[i].length);
- rdma->error_state = -EINVAL;
- return -EINVAL;
}
local->block[i].remote_host_addr =
rdma->dest_blocks[i].remote_host_addr;
--
2.4.3
next reply other threads:[~2015-07-08 14:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 14:26 Dr. David Alan Gilbert (git) [this message]
2015-07-08 14:36 ` [Qemu-devel] [PATCH] RDMA: Reduce restriction on block length match Juan Quintela
2015-07-08 16:55 ` Dr. David Alan Gilbert
2015-07-08 19:06 ` Juan Quintela
2015-07-09 8:08 ` Dr. David Alan Gilbert
-- strict thread matches above, loose matches on Subject: below --
2015-07-08 14:24 Dr. David Alan Gilbert (git)
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=1436365567-27164-1-git-send-email-dgilbert@redhat.com \
--to=dgilbert@redhat.com \
--cc=amit.shah@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).