9005b2a758
This will let threads other than the I/O thread raise QMP events. GIOChannel is thread-safe, and send and receive state is usually well-separated. The only driver that requires some care is the pty driver, where some of the state is shared by the read and write sides. That state is protected with the chr_write_lock too. Reviewed-by: Fam Zheng <famz@redhat.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com> |
||
|---|---|---|
| .. | ||
| arch_init.h | ||
| balloon.h | ||
| blockdev.h | ||
| bt.h | ||
| char.h | ||
| cpus.h | ||
| device_tree.h | ||
| dma.h | ||
| dump-arch.h | ||
| dump.h | ||
| hostmem.h | ||
| iothread.h | ||
| kvm.h | ||
| memory_mapping.h | ||
| os-posix.h | ||
| os-win32.h | ||
| qtest.h | ||
| rng-random.h | ||
| rng.h | ||
| seccomp.h | ||
| sysemu.h | ||
| tpm.h | ||
| tpm_backend.h | ||
| tpm_backend_int.h | ||
| watchdog.h | ||
| xen-mapcache.h | ||