From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
john.stultz@linaro.org, tglx@linutronix.de,
jacob.jun.pan@linux.intel.com,
linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, linaro-kernel@lists.linaro.org,
patches@linaro.org, linus.walleij@stericsson.com
Subject: Re: [PATCH 4/4] ARM: timer-sp: Set dynamic irq affinity
Date: Wed, 27 Feb 2013 10:34:21 +0530 [thread overview]
Message-ID: <512D93D5.3010501@ti.com> (raw)
In-Reply-To: <CAKohpomj1mueL9NETb1xfXTpnKnXCtb9Secu3q5vZTS9dJd0Vg@mail.gmail.com>
On Wednesday 27 February 2013 10:29 AM, Viresh Kumar wrote:
> 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.
>
I should have looked at the patches in order first :)
Sorry for the noise.
Regards,
Santosh
WARNING: multiple messages have this Message-ID (diff)
From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] ARM: timer-sp: Set dynamic irq affinity
Date: Wed, 27 Feb 2013 10:34:21 +0530 [thread overview]
Message-ID: <512D93D5.3010501@ti.com> (raw)
In-Reply-To: <CAKohpomj1mueL9NETb1xfXTpnKnXCtb9Secu3q5vZTS9dJd0Vg@mail.gmail.com>
On Wednesday 27 February 2013 10:29 AM, Viresh Kumar wrote:
> 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.
>
I should have looked at the patches in order first :)
Sorry for the noise.
Regards,
Santosh
WARNING: multiple messages have this Message-ID (diff)
From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
<john.stultz@linaro.org>, <tglx@linutronix.de>,
<jacob.jun.pan@linux.intel.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-pm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linaro-kernel@lists.linaro.org>, <patches@linaro.org>,
<linus.walleij@stericsson.com>
Subject: Re: [PATCH 4/4] ARM: timer-sp: Set dynamic irq affinity
Date: Wed, 27 Feb 2013 10:34:21 +0530 [thread overview]
Message-ID: <512D93D5.3010501@ti.com> (raw)
In-Reply-To: <CAKohpomj1mueL9NETb1xfXTpnKnXCtb9Secu3q5vZTS9dJd0Vg@mail.gmail.com>
On Wednesday 27 February 2013 10:29 AM, Viresh Kumar wrote:
> 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.
>
I should have looked at the patches in order first :)
Sorry for the noise.
Regards,
Santosh
next prev parent reply other threads:[~2013-02-27 5:04 UTC|newest]
Thread overview: 54+ 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 ` Daniel Lezcano
2013-02-26 22:17 ` [PATCH 1/4] time : pass broadcast parameter Daniel Lezcano
2013-02-26 22:17 ` Daniel Lezcano
2013-02-27 5:09 ` Santosh Shilimkar
2013-02-27 5:09 ` Santosh Shilimkar
2013-02-27 5:09 ` Santosh Shilimkar
2013-02-26 22:17 ` [PATCH 2/4] time : set broadcast irq affinity Daniel Lezcano
2013-02-26 22:17 ` Daniel Lezcano
2013-02-27 5:33 ` Santosh Shilimkar
2013-02-27 5:33 ` Santosh Shilimkar
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-02-26 22:17 ` Daniel Lezcano
2013-03-01 1:13 ` Linus Walleij
2013-03-01 1:13 ` Linus Walleij
2013-03-01 8:56 ` Vincent Guittot
2013-03-01 8:56 ` Vincent Guittot
2013-03-01 13:28 ` Rickard Andersson
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-26 22:17 ` Daniel Lezcano
2013-02-27 4:56 ` Santosh Shilimkar
2013-02-27 4:56 ` Santosh Shilimkar
2013-02-27 4:56 ` Santosh Shilimkar
2013-02-27 4:59 ` Viresh Kumar
2013-02-27 4:59 ` Viresh Kumar
2013-02-27 5:04 ` Santosh Shilimkar [this message]
2013-02-27 5:04 ` Santosh Shilimkar
2013-02-27 5:04 ` Santosh Shilimkar
2013-02-27 6:00 ` [PATCH 0/4] time: " Santosh Shilimkar
2013-02-27 6:00 ` Santosh Shilimkar
2013-02-27 6:00 ` Santosh Shilimkar
2013-02-27 10:47 ` Russell King - ARM Linux
2013-02-27 10:47 ` Russell King - ARM Linux
2013-02-27 22:00 ` Thomas Gleixner
2013-02-27 22:00 ` Thomas Gleixner
2013-03-10 17:33 ` Santosh Shilimkar
2013-03-10 17:33 ` Santosh Shilimkar
2013-03-10 17:33 ` Santosh Shilimkar
2013-03-10 18:22 ` Daniel Lezcano
2013-03-10 18:22 ` Daniel Lezcano
2013-03-11 3:24 ` Santosh Shilimkar
2013-03-11 3:24 ` Santosh Shilimkar
2013-03-11 3:24 ` Santosh Shilimkar
2013-03-11 8:40 ` Daniel Lezcano
2013-03-11 8:40 ` Daniel Lezcano
2013-03-11 9:12 ` Santosh Shilimkar
2013-03-11 9:12 ` Santosh Shilimkar
2013-03-11 9:12 ` Santosh Shilimkar
2013-03-11 9:28 ` Rickard Andersson
2013-03-11 9:28 ` Rickard Andersson
2013-03-11 10:29 ` Santosh Shilimkar
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=512D93D5.3010501@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=daniel.lezcano@linaro.org \
--cc=jacob.jun.pan@linux.intel.com \
--cc=john.stultz@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=patches@linaro.org \
--cc=tglx@linutronix.de \
--cc=viresh.kumar@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.