From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] ARM: timer-sp: Set dynamic irq affinity
Date: Wed, 27 Feb 2013 10:29:11 +0530 [thread overview]
Message-ID: <CAKohpomj1mueL9NETb1xfXTpnKnXCtb9Secu3q5vZTS9dJd0Vg@mail.gmail.com> (raw)
In-Reply-To: <512D91E8.6050706@ti.com>
On 27 February 2013 10:26, Santosh Shilimkar <santosh.shilimkar@ti.com> wrote:
> On Wednesday 27 February 2013 03:47 AM, Daniel Lezcano wrote:
>>
>> From: Viresh Kumar <viresh.kumar@linaro.org>
>>
>> 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.
>
> What am I missing here ?
Dynamic affinity will work only if the following flag is set for a
clock_event_device: CLOCK_EVT_FEAT_DYNIRQ, otherwise wakeup
would happen on the cpu to which static affinity was set to.
next prev parent reply other threads:[~2013-02-27 4:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 22:17 [PATCH 0/4] time: dynamic irq affinity Daniel Lezcano
2013-02-26 22:17 ` [PATCH 1/4] time : pass broadcast parameter Daniel Lezcano
2013-02-27 5:09 ` Santosh Shilimkar
2013-02-26 22:17 ` [PATCH 2/4] time : set broadcast irq affinity Daniel Lezcano
2013-02-27 5:33 ` Santosh Shilimkar
2013-02-26 22:17 ` [PATCH 3/4] ARM: nomadik: add dynamic irq flag to the timer Daniel Lezcano
2013-03-01 1:13 ` Linus Walleij
2013-03-01 8:56 ` Vincent Guittot
2013-03-01 13:28 ` Rickard Andersson
2013-02-26 22:17 ` [PATCH 4/4] ARM: timer-sp: Set dynamic irq affinity Daniel Lezcano
2013-02-27 4:56 ` Santosh Shilimkar
2013-02-27 4:59 ` Viresh Kumar [this message]
2013-02-27 5:04 ` Santosh Shilimkar
2013-02-27 6:00 ` [PATCH 0/4] time: " Santosh Shilimkar
2013-02-27 10:47 ` Russell King - ARM Linux
2013-02-27 22:00 ` Thomas Gleixner
2013-03-10 17:33 ` Santosh Shilimkar
2013-03-10 18:22 ` Daniel Lezcano
2013-03-11 3:24 ` Santosh Shilimkar
2013-03-11 8:40 ` Daniel Lezcano
2013-03-11 9:12 ` Santosh Shilimkar
2013-03-11 9:28 ` Rickard Andersson
2013-03-11 10:29 ` Santosh Shilimkar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKohpomj1mueL9NETb1xfXTpnKnXCtb9Secu3q5vZTS9dJd0Vg@mail.gmail.com \
--to=viresh.kumar@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).