diff options
| author | Jan Kiszka <jan.kiszka@siemens.com> | 2011-06-17 11:25:49 +0200 |
|---|---|---|
| committer | Anthony Liguori <aliguori@us.ibm.com> | 2011-07-23 11:26:12 -0500 |
| commit | d25f89c9e91d6c46b85969922411a211a6347a7d (patch) | |
| tree | 6ef37246ff23527e8bc62fcf4f271bded16619d3 /hw/usb-serial.c | |
| parent | 17604dac28b2410c021a4a52dcfa58e8803dfb24 (diff) | |
| download | qemu-d25f89c9e91d6c46b85969922411a211a6347a7d.zip qemu-d25f89c9e91d6c46b85969922411a211a6347a7d.tar.gz qemu-d25f89c9e91d6c46b85969922411a211a6347a7d.tar.bz2 | |
Register Linux dyntick timer as per-thread signal
Derived from kvm-tool patch
http://thread.gmane.org/gmane.comp.emulators.kvm.devel/74309
Ingo Molnar pointed out that sending the timer signal to the whole
process, just blocking it everywhere, is suboptimal with an increasing
number of threads. QEMU is also using this pattern so far.
Linux provides a (non-portable) way to restrict the signal to a single
thread: We can use SIGEV_THREAD_ID unless we are forced to emulate
signalfd via an additional thread. That case could theoretically be
optimized as well, but it doesn't look worth bothering.
Reviewed-by: Richard Henderson <rth@twiddle.net>
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Diffstat (limited to 'hw/usb-serial.c')
0 files changed, 0 insertions, 0 deletions