migration/multifd: Allow zero pages in file migration
Currently, it's an error to have no data pages in the multifd file migration because zero page detection is done in the migration thread and zero pages don't reach multifd. This is enforced with the pages->num assert. We're about to add zero page detection on the multifd thread. Fix the file_write_ramblock_iov() to stop considering p->iovs_num=0 an error. Signed-off-by: Fabiano Rosas <farosas@suse.de> Link: https://lore.kernel.org/r/20240311180015.3359271-2-hao.xiang@linux.dev Signed-off-by: Peter Xu <peterx@redhat.com>
This commit is contained in:
parent
c9539d9b14
commit
44fe138edc
@ -159,7 +159,7 @@ void file_start_incoming_migration(FileMigrationArgs *file_args, Error **errp)
|
|||||||
int file_write_ramblock_iov(QIOChannel *ioc, const struct iovec *iov,
|
int file_write_ramblock_iov(QIOChannel *ioc, const struct iovec *iov,
|
||||||
int niov, RAMBlock *block, Error **errp)
|
int niov, RAMBlock *block, Error **errp)
|
||||||
{
|
{
|
||||||
ssize_t ret = -1;
|
ssize_t ret = 0;
|
||||||
int i, slice_idx, slice_num;
|
int i, slice_idx, slice_num;
|
||||||
uintptr_t base, next, offset;
|
uintptr_t base, next, offset;
|
||||||
size_t len;
|
size_t len;
|
||||||
|
Loading…
Reference in New Issue
Block a user