From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:59258)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <cerbere@gmail.com>) id 1QXERa-0001J7-Kz
	for qemu-devel@nongnu.org; Thu, 16 Jun 2011 11:25:22 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <cerbere@gmail.com>) id 1QXERY-0007Sz-LV
	for qemu-devel@nongnu.org; Thu, 16 Jun 2011 11:25:18 -0400
Received: from mail-pv0-f173.google.com ([74.125.83.173]:60876)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <cerbere@gmail.com>) id 1QXERY-0007SX-4G
	for qemu-devel@nongnu.org; Thu, 16 Jun 2011 11:25:16 -0400
Received: by pvg3 with SMTP id 3so1236317pvg.4
	for <qemu-devel@nongnu.org>; Thu, 16 Jun 2011 08:25:14 -0700 (PDT)
MIME-Version: 1.0
In-Reply-To: <4DF9CD7E.5020509@siemens.com>
References: <4DF9CD7E.5020509@siemens.com>
From: Alexandre Raymond <cerbere@gmail.com>
Date: Thu, 16 Jun 2011 11:24:54 -0400
Message-ID: <BANLkTinarwP=AwG_KFm0B3moFYbQOQ2SbQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [Qemu-devel] [RFC][PATCH] Register Linux dyntick timer as
 per-thread signal
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, Anthony Liguori <aliguori@us.ibm.com>, qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>, Sasha Levin <levinsasha928@gmail.com>

Hi Jan,

On Thu, Jun 16, 2011 at 5:31 AM, Jan Kiszka <jan.kiszka@siemens.com> 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.

I am not familiar with this code, but don't you already need to block
SIGALRM properly in all threads for OSes != Linux ? If so, isn't this
patch redundant?

Alexandre