Paolo Bonzini a59629fcc6 rcu: do not create thread in pthread_atfork callback ... If QEMU forks after the CPU threads have been created, qemu_mutex_lock_iothread will not be able to do qemu_cpu_kick_thread. There is no solution other than assuming that forks after the CPU threads have been created will end up in an exec. Forks before the CPU threads have been created (such as -daemonize) have to call rcu_after_fork manually. Notably, the oxygen theme for GTK+ forks and shows a "No such process" error without this patch. This patch can be reverted once the iothread loses the "kick the TCG thread" magic. User-mode emulation does not use the iothread, so it can also call rcu_after_fork. Reported by: Dr. David Alan Gilbert <dgilbert@redhat.com> Tested by: Dr. David Alan Gilbert <dgilbert@redhat.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>		2015-04-01 10:06:38 +02:00
..
acl.h
aes.h
atomic.h
bitmap.h
bitops.h
bswap.h
compatfd.h
compiler.h
config-file.h
crc32c.h
envlist.h
error-report.h
event_notifier.h
fifo8.h
hbitmap.h
host-utils.h
int128.h
iov.h
log.h
main-loop.h
module.h
notify.h
option_int.h
option.h
osdep.h
queue.h
range.h
ratelimit.h
rcu_queue.h
rcu.h	rcu: do not create thread in pthread_atfork callback	2015-04-01 10:06:38 +02:00
readline.h
rfifolock.h
seqlock.h
sockets.h
thread-posix.h
thread-win32.h
thread.h
throttle.h
timer.h
tls.h
typedefs.h
uri.h
xattr.h