Register Linux dyntick timer as per-thread signal
commitd25f89c9e91d6c46b85969922411a211a6347a7d
authorJan Kiszka <jan.kiszka@siemens.com>
Fri, 17 Jun 2011 09:25:49 +0000 (17 11:25 +0200)
committerAnthony Liguori <aliguori@us.ibm.com>
Sat, 23 Jul 2011 16:26:12 +0000 (23 11:26 -0500)
tree6ef37246ff23527e8bc62fcf4f271bded16619d3
parent17604dac28b2410c021a4a52dcfa58e8803dfb24
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>
compatfd.c
compatfd.h
qemu-timer.c