Re: [libvirt PATCH] qemu: Update asyncOwnerAPI when entering async job phase

2021-03-22 Thread Jiri Denemark
On Mon, Mar 22, 2021 at 11:17:12 +0100, Michal Privoznik wrote: > On 3/19/21 10:42 PM, Jiri Denemark wrote: > > In case an async job spans multiple APIs (e.g., incoming migration) the > > API that started the job is recorded as the asyncOwnerAPI even though it > > is no longer running and the

Re: [libvirt PATCH] qemu: Update asyncOwnerAPI when entering async job phase

2021-03-22 Thread Michal Privoznik
On 3/19/21 10:42 PM, Jiri Denemark wrote: In case an async job spans multiple APIs (e.g., incoming migration) the API that started the job is recorded as the asyncOwnerAPI even though it is no longer running and the owner thread is updated properly to the one currently handling the job. Let's

Re: [libvirt PATCH] qemu: Update asyncOwnerAPI when entering async job phase

2021-03-22 Thread Erik Skultety
On Fri, Mar 19, 2021 at 10:42:25PM +0100, Jiri Denemark wrote: > In case an async job spans multiple APIs (e.g., incoming migration) the > API that started the job is recorded as the asyncOwnerAPI even though it > is no longer running and the owner thread is updated properly to the one > currently

[libvirt PATCH] qemu: Update asyncOwnerAPI when entering async job phase

2021-03-19 Thread Jiri Denemark
In case an async job spans multiple APIs (e.g., incoming migration) the API that started the job is recorded as the asyncOwnerAPI even though it is no longer running and the owner thread is updated properly to the one currently handling the job. Let's also update asyncOwnerAPI to make it more