Thanks for your review. I will change it in the next version(V2).
-----Original Message-----
From: Markus Armbruster [mailto:arm...@redhat.com]
Sent: Monday, January 13, 2020 11:30 PM
To: fengzhimin <fengzhim...@huawei.com>
Cc: quint...@redhat.com; dgilb...@redhat.com; ebl...@redhat.com;
jemmy858...@gmail.com; qemu-devel@nongnu.org; Zhanghailiang
<zhang.zhanghaili...@huawei.com>
Subject: Re: [PATCH RFC 01/12] migration: Add multiRDMA capability support
Zhimin Feng <fengzhim...@huawei.com> writes:
> From: fengzhimin <fengzhim...@huawei.com>
>
> Signed-off-by: fengzhimin <fengzhim...@huawei.com>
> ---
[...]
> diff --git a/qapi/migration.json b/qapi/migration.json index
> b7348d0c8b..c995ffdc4c 100644
> --- a/qapi/migration.json
> +++ b/qapi/migration.json
> @@ -421,6 +421,8 @@
> # @validate-uuid: Send the UUID of the source to allow the destination
> # to ensure it is the same. (since 4.2)
> #
> +# @multirdma: Use more than one channels for rdma migration. (since
> +4.2) #
> # Since: 1.2
> ##
> { 'enum': 'MigrationCapability',
> @@ -428,7 +430,7 @@
> 'compress', 'events', 'postcopy-ram', 'x-colo', 'release-ram',
> 'block', 'return-path', 'pause-before-switchover', 'multifd',
> 'dirty-bitmaps', 'postcopy-blocktime', 'late-block-activate',
> - 'x-ignore-shared', 'validate-uuid' ] }
> + 'x-ignore-shared', 'validate-uuid', 'multirdma' ] }
>
> ##
> # @MigrationCapabilityStatus:
Spell it multi-rdma?
