On Mon, Nov 27, 2017 at 11:04:00AM +, Dr. David Alan Gilbert wrote:
> * Peter Xu (pet...@redhat.com) wrote:
> > On Mon, Nov 27, 2017 at 10:44:26AM +, Dr. David Alan Gilbert wrote:
> >
> > [...]
> >
> > > > >
> > > > > But then I added a break on pthread_mutex_lock, and I've got
> > > > >
* Peter Xu (pet...@redhat.com) wrote:
> On Mon, Nov 27, 2017 at 10:44:26AM +, Dr. David Alan Gilbert wrote:
>
> [...]
>
> > > >
> > > > But then I added a break on pthread_mutex_lock, and I've got
> > > > this set caused by qemu_start_incoming_migration sending a
> > > > MIGRATION_STATUS_SET
On Mon, Nov 27, 2017 at 10:44:26AM +, Dr. David Alan Gilbert wrote:
[...]
> > >
> > > But then I added a break on pthread_mutex_lock, and I've got
> > > this set caused by qemu_start_incoming_migration sending a
> > > MIGRATION_STATUS_SETUP event:
> > >
> > > #1 0x55ba6eba in qemu_
* Peter Xu (pet...@redhat.com) wrote:
> On Fri, Nov 24, 2017 at 01:14:53PM +, Dr. David Alan Gilbert wrote:
> > * Peter Xu (pet...@redhat.com) wrote:
> > > So it can get rid of being run on main thread.
> > >
> > > Signed-off-by: Peter Xu
> >
> > Last time I asked if you were sure that we di
On Fri, Nov 24, 2017 at 01:14:53PM +, Dr. David Alan Gilbert wrote:
> * Peter Xu (pet...@redhat.com) wrote:
> > So it can get rid of being run on main thread.
> >
> > Signed-off-by: Peter Xu
>
> Last time I asked if you were sure that we didn't do locking,
> and you explained that we end up
* Peter Xu (pet...@redhat.com) wrote:
> So it can get rid of being run on main thread.
>
> Signed-off-by: Peter Xu
Last time I asked if you were sure that we didn't do locking,
and you explained that we end up just setting up a callback
that happens in the mainloop, and this shouldn't take a loc
So it can get rid of being run on main thread.
Signed-off-by: Peter Xu
---
qapi/migration.json | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/qapi/migration.json b/qapi/migration.json
index bbc4671ded..95098072dd 100644
--- a/qapi/migration.json
+++ b/qapi/migration.json
@
