Re: [PATCH v5 19/20] job.c: enable job lock/unlock and remove Aiocontext locks

2022-03-10 Thread Emanuele Giuseppe Esposito
Am 08/03/2022 um 15:04 schrieb Stefan Hajnoczi: > On Tue, Feb 08, 2022 at 09:35:12AM -0500, Emanuele Giuseppe Esposito wrote: >> diff --git a/include/qemu/job.h b/include/qemu/job.h >> index ca46e46f5b..574110a1f2 100644 >> --- a/include/qemu/job.h >> +++ b/include/qemu/job.h >> @@ -75,11 +75,14

Re: [PATCH v5 19/20] job.c: enable job lock/unlock and remove Aiocontext locks

2022-03-08 Thread Stefan Hajnoczi
On Tue, Feb 08, 2022 at 09:35:12AM -0500, Emanuele Giuseppe Esposito wrote: > diff --git a/include/qemu/job.h b/include/qemu/job.h > index ca46e46f5b..574110a1f2 100644 > --- a/include/qemu/job.h > +++ b/include/qemu/job.h > @@ -75,11 +75,14 @@ typedef struct Job { > ProgressMeter progress; >

[PATCH v5 19/20] job.c: enable job lock/unlock and remove Aiocontext locks

2022-02-08 Thread Emanuele Giuseppe Esposito
Change the job_{lock/unlock} and macros to use job_mutex. Now that they are not nop anymore, remove the aiocontext to avoid deadlocks. Therefore: - when possible, remove completely the aiocontext lock/unlock pair - if it is used by some other functions too, reduce the locking section as much as p