huang...@chinatelecom.cn writes:
> From: Hyman Huang(黄勇) <huang...@chinatelecom.cn>
>
> Export dirty limit throttle time and estimated ring full
> time, through which we can observe the process of dirty
> limit during live migration.
>
> Signed-off-by: Hyman Huang(黄勇) <huang...@chinatelecom.cn>
[...]
> diff --git a/qapi/migration.json b/qapi/migration.json
> index af6b2da..62db5cb 100644
> --- a/qapi/migration.json
> +++ b/qapi/migration.json
> @@ -242,6 +242,12 @@
> # Present and non-empty when migration is blocked.
> # (since 6.0)
> #
> +# @dirty-limit-throttle-us-per-full: Throttle time (us) during the period of
> +# dirty ring full (since 7.1)
> +#
> +# @dirty-limit-us-ring-full: Estimated periodic time (us) of dirty ring full.
> +# (since 7.1)
8.0
In review of v1, I asked you to explain the two members' meaning,
i.e. what exactly is being measured. You replied. Would it make sense
to work your explanation into the doc comments?
> +#
> # Since: 0.14
> ##
> { 'struct': 'MigrationInfo',
> @@ -259,7 +265,9 @@
> '*postcopy-blocktime' : 'uint32',
> '*postcopy-vcpu-blocktime': ['uint32'],
> '*compression': 'CompressionStats',
> - '*socket-address': ['SocketAddress'] } }
> + '*socket-address': ['SocketAddress'],
> + '*dirty-limit-throttle-us-per-full': 'int64',
> + '*dirty-limit-us-ring-full': 'int64'} }
>
> ##
> # @query-migrate:
[...]
