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
petalogix-s3adsp1800.dtb
Ð
þí C 8 ( 3 Ø xlnx,microblaze &testing memory@90000000 ,memory 8 chosen <console=ttyUL0,115200 E/plb@0/serial@84000000 cpus W cpu@0 ]¹¬ xlnx,microblaze-7.10.d m ~ÿÿÿ ¡ ,cpu ® ¿ÿÿÿ Ð â µblaze,7.10.d 8 ﹬ * ? S h s ~ Å Û ð / G _
uspartan3adsp § º É Ô ß ê +
Emicroblaze_0 S e | § º Î Ý ó ) A J Y h w ª º Ç Ø ì % 5 H U h plb@0 xlnx,plb-v46-1.03.a simple-bus | ethernet@81000000 xlnx,xps-ethernetlite-2.00.a ,network 8 ±
uspartan3adsp ½ Ï flash@a0000000 á "