From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:50650) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QXD4V-0003J9-0b for qemu-devel@nongnu.org; Thu, 16 Jun 2011 09:57:27 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QXD4K-000372-DO for qemu-devel@nongnu.org; Thu, 16 Jun 2011 09:57:22 -0400 Received: from fallback.mail.elte.hu ([157.181.151.13]:35484) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QXD4J-00036a-Oj for qemu-devel@nongnu.org; Thu, 16 Jun 2011 09:57:12 -0400 Received: from mx2.mail.elte.hu ([157.181.151.9]) by fallback.mail.elte.hu with esmtp (Exim) id 1QX9pF-0003bl-P6 from for ; Thu, 16 Jun 2011 12:29:25 +0200 Date: Thu, 16 Jun 2011 12:26:06 +0200 From: Ingo Molnar Message-ID: <20110616102606.GA24541@elte.hu> References: <4DF9CD7E.5020509@siemens.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4DF9CD7E.5020509@siemens.com> Subject: Re: [Qemu-devel] [RFC][PATCH] Register Linux dyntick timer as per-thread signal List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: Anthony Liguori , kvm , Asias He , qemu-devel , Pekka Enberg , Sasha Levin , Paolo Bonzini * Jan Kiszka wrote: > 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 using this pattern so far. > > But Linux provides a (non-portable) way to restrict the signal to a > single thread: 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. Would be nice to mention it in the changelog that the context and motivation for my remark was a patch sent for tools/kvm/ by Asias He: kvm tools: Block SIGALRM for vcpu thread using sig_block() helper Thanks, Ingo