From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: too many timer retries happen when do local timer swtich with broadcast timer
Date: Fri, 22 Feb 2013 15:37:42 +0530 [thread overview]
Message-ID: <5127436E.4040100@ti.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1302212214020.22263@ionos>
Thomas,
On Friday 22 February 2013 03:49 AM, Thomas Gleixner wrote:
> On Thu, 21 Feb 2013, Santosh Shilimkar wrote:
>> On Thursday 21 February 2013 07:18 PM, Thomas Gleixner wrote:
>>> find below a completely untested patch, which should address that issue.
>>>
>> After looking at the thread, I tried to see the issue on OMAP and could
>> see the same issue as Jason.
>
> That's interesting. We have the same issue on x86 since 2007 and
> nobody noticed ever. It's basically the same problem there, but it
> seems that on x86 getting out of those low power states is way slower
> than the minimal reprogramming delta which is used to enforce the
> local timer to fire after the wakeup.
>
> I'm still amazed that as Jason stated a 1us reprogramming delta is
> sufficient to get this ping-pong going. I somehow doubt that, but
> maybe ARM is really that fast :)
>
>> Your patch fixes the retries on both CPUs on my dual core machine. So
>> you use my tested by if you need one.
>
> They are always welcome.
>
BTW, Lorenzo off-list mentioned to me about warning in boot-up
which I missed while testing your patch. It will take bit more
time for me to look into it and hence thought of reporting it.
[ 2.186126] ------------[ cut here ]------------
[ 2.190979] WARNING: at kernel/time/tick-broadcast.c:501
tick_broadcast_oneshot_control+0x1c0/0x21c()
[ 2.200622] Modules linked in:
[ 2.203826] [<c001bfe4>] (unwind_backtrace+0x0/0xf0) from
[<c0047d6c>] (warn_slowpath_common+0x4c/0x64)
[ 2.213653] [<c0047d6c>] (warn_slowpath_common+0x4c/0x64) from
[<c0047da0>] (warn_slowpath_null+0x1c/0x24)
[ 2.223754] [<c0047da0>] (warn_slowpath_null+0x1c/0x24) from
[<c009336c>] (tick_broadcast_oneshot_control+0x1c0/0x21c)
[ 2.234924] [<c009336c>] (tick_broadcast_oneshot_control+0x1c0/0x21c)
from [<c00928dc>] (tick_notify+0x23c/0x42c)
[ 2.245666] [<c00928dc>] (tick_notify+0x23c/0x42c) from [<c0539a3c>]
(notifier_call_chain+0x44/0x84)
[ 2.255218] [<c0539a3c>] (notifier_call_chain+0x44/0x84) from
[<c0071068>] (raw_notifier_call_chain+0x18/0x20)
[ 2.265686] [<c0071068>] (raw_notifier_call_chain+0x18/0x20) from
[<c0091c70>] (clockevents_notify+0x2c/0x174)
[ 2.276123] [<c0091c70>] (clockevents_notify+0x2c/0x174) from
[<c0035294>] (omap_enter_idle_smp+0x3c/0x120)
[ 2.286315] [<c0035294>] (omap_enter_idle_smp+0x3c/0x120) from
[<c042e504>] (cpuidle_enter+0x14/0x18)
[ 2.295928] [<c042e504>] (cpuidle_enter+0x14/0x18) from [<c042ef14>]
(cpuidle_wrap_enter+0x34/0xa0)
[ 2.305389] [<c042ef14>] (cpuidle_wrap_enter+0x34/0xa0) from
[<c042eb20>] (cpuidle_idle_call+0xe0/0x328)
[ 2.315307] [<c042eb20>] (cpuidle_idle_call+0xe0/0x328) from
[<c0015100>] (cpu_idle+0x8c/0x11c)
[ 2.324401] [<c0015100>] (cpu_idle+0x8c/0x11c) from [<c073d7ac>]
(start_kernel+0x2b0/0x300)
[ 2.333129] ---[ end trace 6fe1f7b4606a9e20 ]---
WARNING: multiple messages have this Message-ID (diff)
From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Jason Liu <liu.h.jason@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Subject: Re: too many timer retries happen when do local timer swtich with broadcast timer
Date: Fri, 22 Feb 2013 15:37:42 +0530 [thread overview]
Message-ID: <5127436E.4040100@ti.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1302212214020.22263@ionos>
Thomas,
On Friday 22 February 2013 03:49 AM, Thomas Gleixner wrote:
> On Thu, 21 Feb 2013, Santosh Shilimkar wrote:
>> On Thursday 21 February 2013 07:18 PM, Thomas Gleixner wrote:
>>> find below a completely untested patch, which should address that issue.
>>>
>> After looking at the thread, I tried to see the issue on OMAP and could
>> see the same issue as Jason.
>
> That's interesting. We have the same issue on x86 since 2007 and
> nobody noticed ever. It's basically the same problem there, but it
> seems that on x86 getting out of those low power states is way slower
> than the minimal reprogramming delta which is used to enforce the
> local timer to fire after the wakeup.
>
> I'm still amazed that as Jason stated a 1us reprogramming delta is
> sufficient to get this ping-pong going. I somehow doubt that, but
> maybe ARM is really that fast :)
>
>> Your patch fixes the retries on both CPUs on my dual core machine. So
>> you use my tested by if you need one.
>
> They are always welcome.
>
BTW, Lorenzo off-list mentioned to me about warning in boot-up
which I missed while testing your patch. It will take bit more
time for me to look into it and hence thought of reporting it.
[ 2.186126] ------------[ cut here ]------------
[ 2.190979] WARNING: at kernel/time/tick-broadcast.c:501
tick_broadcast_oneshot_control+0x1c0/0x21c()
[ 2.200622] Modules linked in:
[ 2.203826] [<c001bfe4>] (unwind_backtrace+0x0/0xf0) from
[<c0047d6c>] (warn_slowpath_common+0x4c/0x64)
[ 2.213653] [<c0047d6c>] (warn_slowpath_common+0x4c/0x64) from
[<c0047da0>] (warn_slowpath_null+0x1c/0x24)
[ 2.223754] [<c0047da0>] (warn_slowpath_null+0x1c/0x24) from
[<c009336c>] (tick_broadcast_oneshot_control+0x1c0/0x21c)
[ 2.234924] [<c009336c>] (tick_broadcast_oneshot_control+0x1c0/0x21c)
from [<c00928dc>] (tick_notify+0x23c/0x42c)
[ 2.245666] [<c00928dc>] (tick_notify+0x23c/0x42c) from [<c0539a3c>]
(notifier_call_chain+0x44/0x84)
[ 2.255218] [<c0539a3c>] (notifier_call_chain+0x44/0x84) from
[<c0071068>] (raw_notifier_call_chain+0x18/0x20)
[ 2.265686] [<c0071068>] (raw_notifier_call_chain+0x18/0x20) from
[<c0091c70>] (clockevents_notify+0x2c/0x174)
[ 2.276123] [<c0091c70>] (clockevents_notify+0x2c/0x174) from
[<c0035294>] (omap_enter_idle_smp+0x3c/0x120)
[ 2.286315] [<c0035294>] (omap_enter_idle_smp+0x3c/0x120) from
[<c042e504>] (cpuidle_enter+0x14/0x18)
[ 2.295928] [<c042e504>] (cpuidle_enter+0x14/0x18) from [<c042ef14>]
(cpuidle_wrap_enter+0x34/0xa0)
[ 2.305389] [<c042ef14>] (cpuidle_wrap_enter+0x34/0xa0) from
[<c042eb20>] (cpuidle_idle_call+0xe0/0x328)
[ 2.315307] [<c042eb20>] (cpuidle_idle_call+0xe0/0x328) from
[<c0015100>] (cpu_idle+0x8c/0x11c)
[ 2.324401] [<c0015100>] (cpu_idle+0x8c/0x11c) from [<c073d7ac>]
(start_kernel+0x2b0/0x300)
[ 2.333129] ---[ end trace 6fe1f7b4606a9e20 ]---
next prev parent reply other threads:[~2013-02-22 10:07 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 11:16 too many timer retries happen when do local timer swtich with broadcast timer Jason Liu
2013-02-20 11:16 ` Jason Liu
2013-02-20 13:33 ` Thomas Gleixner
2013-02-20 13:33 ` Thomas Gleixner
2013-02-21 6:16 ` Jason Liu
2013-02-21 6:16 ` Jason Liu
2013-02-21 9:36 ` Thomas Gleixner
2013-02-21 9:36 ` Thomas Gleixner
2013-02-21 10:50 ` Jason Liu
2013-02-21 10:50 ` Jason Liu
2013-02-21 13:48 ` Thomas Gleixner
2013-02-21 13:48 ` Thomas Gleixner
2013-02-21 15:12 ` Santosh Shilimkar
2013-02-21 15:12 ` Santosh Shilimkar
2013-02-21 22:19 ` Thomas Gleixner
2013-02-21 22:19 ` Thomas Gleixner
2013-02-22 10:07 ` Santosh Shilimkar [this message]
2013-02-22 10:07 ` Santosh Shilimkar
2013-02-22 10:24 ` Thomas Gleixner
2013-02-22 10:24 ` Thomas Gleixner
2013-02-22 10:30 ` Santosh Shilimkar
2013-02-22 10:30 ` Santosh Shilimkar
2013-02-22 10:31 ` Lorenzo Pieralisi
2013-02-22 10:31 ` Lorenzo Pieralisi
2013-02-22 11:02 ` Santosh Shilimkar
2013-02-22 11:02 ` Santosh Shilimkar
2013-02-22 12:07 ` Thomas Gleixner
2013-02-22 12:07 ` Thomas Gleixner
2013-02-22 14:48 ` Lorenzo Pieralisi
2013-02-22 14:48 ` Lorenzo Pieralisi
2013-02-22 15:03 ` Thomas Gleixner
2013-02-22 15:03 ` Thomas Gleixner
2013-02-22 15:26 ` Lorenzo Pieralisi
2013-02-22 15:26 ` Lorenzo Pieralisi
2013-02-22 18:52 ` Thomas Gleixner
2013-02-22 18:52 ` Thomas Gleixner
2013-02-25 6:12 ` Santosh Shilimkar
2013-02-25 6:12 ` Santosh Shilimkar
2013-02-25 6:38 ` Jason Liu
2013-02-25 6:38 ` Jason Liu
2013-02-25 13:34 ` Lorenzo Pieralisi
2013-02-25 13:34 ` Lorenzo Pieralisi
2013-02-22 10:28 ` Lorenzo Pieralisi
2013-02-22 10:28 ` Lorenzo Pieralisi
2013-02-22 10:26 ` Jason Liu
2013-02-22 10:26 ` Jason Liu
2013-02-21 10:35 ` Lorenzo Pieralisi
2013-02-21 10:35 ` Lorenzo Pieralisi
2013-02-21 10:49 ` Jason Liu
2013-02-21 10:49 ` Jason Liu
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=5127436E.4040100@ti.com \
--to=santosh.shilimkar@ti.com \
--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 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.