* Peter Xu (pet...@redhat.com) wrote:
> So it can get rid of being run on main thread.
>
> Signed-off-by: Peter Xu <pet...@redhat.com>
> ---
> qapi/migration.json | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/qapi/migration.json b/qapi/migration.json
> index ee2b3b8..dedc4f8 100644
> --- a/qapi/migration.json
> +++ b/qapi/migration.json
> @@ -986,7 +986,8 @@
> # <- { "return": {} }
> #
> ##
> -{ 'command': 'migrate-incoming', 'data': {'uri': 'str' } }
> +{ 'command': 'migrate-incoming', 'data': {'uri': 'str' },
> + 'allow-oob': true }
Are you completely convinced migrate-incoming is non-blocking?
What about during the tls handshake if tls is enabled?
(We only set non-blocking on the fd later)
I don't understand in this structure on which thread
process_incoming_migration_co gets run.
Dave
> ##
> # @xen-save-devices-state:
> --
> 2.7.4
>
--
Dr. David Alan Gilbert / dgilb...@redhat.com / Manchester, UK
