* Peter Xu (pet...@redhat.com) wrote:
> On Wed, Feb 28, 2018 at 05:43:50PM +, Dr. David Alan Gilbert wrote:
> > * Peter Xu (pet...@redhat.com) wrote:
> > > The old incoming migration is running in main thread and default
> > > gcontext. With the new qio_channel_add_watch_full() we can now let
On Wed, Feb 28, 2018 at 09:10:58AM +, Daniel P. Berrangé wrote:
> On Wed, Feb 28, 2018 at 01:06:23PM +0800, Peter Xu wrote:
> > 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
On Wed, Feb 28, 2018 at 05:43:50PM +, Dr. David Alan Gilbert wrote:
> * Peter Xu (pet...@redhat.com) wrote:
> > 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 th
* Peter Xu (pet...@redhat.com) wrote:
> 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
On Wed, Feb 28, 2018 at 01:06:23PM +0800, Peter Xu wrote:
> 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.
