On Fri, Feb 22, 2019 at 11:14:10AM +0800, Peter Xu wrote:
> Only sending an init-done message using lock+cond seems an overkill to
> me. Replacing it with a simpler semaphore.
>
> Meanwhile, init the semaphore unconditionally, then we can destroy it
> unconditionally too in finalize which seems c
Hi
On Fri, Feb 22, 2019 at 10:33 AM Paolo Bonzini wrote:
>
> On 22/02/19 07:36, Peter Xu wrote:
> > On Fri, Feb 22, 2019 at 07:25:16AM +0100, Marc-André Lureau wrote:
> >> Hi
> >>
> >> On Fri, Feb 22, 2019 at 4:14 AM Peter Xu wrote:
> >>>
> >>> Only sending an init-done message using lock+cond s
On 22/02/19 07:36, Peter Xu wrote:
> On Fri, Feb 22, 2019 at 07:25:16AM +0100, Marc-André Lureau wrote:
>> Hi
>>
>> On Fri, Feb 22, 2019 at 4:14 AM Peter Xu wrote:
>>>
>>> Only sending an init-done message using lock+cond seems an overkill to
>>> me. Replacing it with a simpler semaphore.
>>>
>>>
On Fri, Feb 22, 2019 at 07:25:16AM +0100, Marc-André Lureau wrote:
> Hi
>
> On Fri, Feb 22, 2019 at 4:14 AM Peter Xu wrote:
> >
> > Only sending an init-done message using lock+cond seems an overkill to
> > me. Replacing it with a simpler semaphore.
> >
> > Meanwhile, init the semaphore uncondit
Hi
On Fri, Feb 22, 2019 at 4:14 AM Peter Xu wrote:
>
> Only sending an init-done message using lock+cond seems an overkill to
> me. Replacing it with a simpler semaphore.
>
> Meanwhile, init the semaphore unconditionally, then we can destroy it
> unconditionally too in finalize which seems clean
Only sending an init-done message using lock+cond seems an overkill to
me. Replacing it with a simpler semaphore.
Meanwhile, init the semaphore unconditionally, then we can destroy it
unconditionally too in finalize which seems cleaner.
Signed-off-by: Peter Xu
---
include/sysemu/iothread.h |
