Revision 9a3e52e3465f85d203d0fd2910ca3625b3c45420 authored by Wolfgang Bumiller on 25 September 2018, 08:15:06 UTC, committed by Markus Armbruster on 06 November 2018, 16:02:49 UTC
monitor_resume() and monitor_suspend() both want to "kick" the I/O thread if it is there, but in monitor_suspend() lacked the use_io_thread flag condition. This is required when we later only spawn the thread on first use. Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com> Reviewed-by: Eric Blake <eblake@redhat.com> Reviewed-by: Peter Xu <peterx@redhat.com> Message-Id: <20180925081507.11873-2-w.bumiller@proxmox.com> Signed-off-by: Markus Armbruster <armbru@redhat.com>
1 parent 0ca70f1
| File | Mode | Size |
|---|---|---|
| Makefile.objs | -rw-r--r-- | 102 bytes |
| container.c | -rw-r--r-- | 1.1 KB |
| cpu.c | -rw-r--r-- | 12.0 KB |
| object.c | -rw-r--r-- | 63.0 KB |
| object_interfaces.c | -rw-r--r-- | 4.8 KB |
| qom-qobject.c | -rw-r--r-- | 1.2 KB |
| trace-events | -rw-r--r-- | 339 bytes |
Computing file changes ...
