From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759917Ab3B0EzH (ORCPT ); Tue, 26 Feb 2013 23:55:07 -0500 Received: from arroyo.ext.ti.com ([192.94.94.40]:36754 "EHLO arroyo.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758491Ab3B0EzE (ORCPT ); Tue, 26 Feb 2013 23:55:04 -0500 Message-ID: <512D91E8.6050706@ti.com> Date: Wed, 27 Feb 2013 10:26:08 +0530 From: Santosh Shilimkar User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Daniel Lezcano CC: , , , , , , , , , Subject: Re: [PATCH 4/4] ARM: timer-sp: Set dynamic irq affinity References: <1361917047-29230-1-git-send-email-daniel.lezcano@linaro.org> <1361917047-29230-5-git-send-email-daniel.lezcano@linaro.org> In-Reply-To: <1361917047-29230-5-git-send-email-daniel.lezcano@linaro.org> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wednesday 27 February 2013 03:47 AM, Daniel Lezcano wrote: > From: Viresh Kumar > > When a cpu goes to a deep idle state where its local timer is shutdown, it > notifies the time frame work to use the broadcast timer instead. > > Unfortunately, the broadcast device could wake up any CPU, including an idle one > which is not concerned by the wake up at all. > Broad-cast device will only open the CPU for which the timer IRQ affined to. And infact with subject series the affinity also is updated for the CPU which owns the last timer expiry event. > This implies, in the worst case, an idle CPU will wake up to send an IPI to > another idle cpu. > > This patch fixes this for ARM platforms using timer-sp, by setting > CLOCK_EVT_FEAT_DYNIRQ feature. > > Signed-off-by: Viresh Kumar > Signed-off-by: Daniel Lezcano > --- What am I missing here ? Regards, Santosh