diff options
| author | Peter Xu <peterx@redhat.com> | 2018-05-02 18:47:17 +0800 |
|---|---|---|
| committer | Juan Quintela <quintela@redhat.com> | 2018-05-15 20:24:27 +0200 |
| commit | e89f5ff2c305a335dd42091ab379f1e38df6f161 (patch) | |
| tree | 5721baf3c96962824f3274f604f8990a6bba1420 /qapi | |
| parent | 8c4598f2b1f65ca063d0d5e0dc7f621e2023a0fd (diff) | |
| download | qemu-e89f5ff2c305a335dd42091ab379f1e38df6f161.zip qemu-e89f5ff2c305a335dd42091ab379f1e38df6f161.tar.gz qemu-e89f5ff2c305a335dd42091ab379f1e38df6f161.tar.bz2 | |
migration: let incoming side use thread context
The old incoming migration is running in main thread and default
gcontext. With the new qio_channel_add_watch_full() we can now let it
run in the thread's own gcontext (if there is one).
Currently this patch does nothing alone. But when any of the incoming
migration is run in another iothread (e.g., the upcoming migrate-recover
command), this patch will bind the incoming logic to the iothread
instead of the main thread (which may already get page faulted and
hanged).
RDMA is not considered for now since it's not even using the QIO watch
framework at all.
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Reviewed-by: Juan Quintela <quintela@redhat.com>
Signed-off-by: Peter Xu <peterx@redhat.com>
Message-Id: <20180502104740.12123-2-peterx@redhat.com>
Signed-off-by: Juan Quintela <quintela@redhat.com>
Diffstat (limited to 'qapi')
0 files changed, 0 insertions, 0 deletions