From: Thomas Gleixner <tglx@linutronix.de> To: Santosh Shilimkar <santosh.shilimkar@ti.com> Cc: Jason Liu <liu.h.jason@gmail.com>, LKML <linux-kernel@vger.kernel.org>, linux-arm-kernel@lists.infradead.org Subject: Re: too many timer retries happen when do local timer swtich with broadcast timer Date: Thu, 21 Feb 2013 23:19:18 +0100 (CET) [thread overview] Message-ID: <alpine.LFD.2.02.1302212214020.22263@ionos> (raw) In-Reply-To: <51263975.20906@ti.com> 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. > Tested-by: Santosh Shilimkar <santosh.shilimkar@ti.com> > > Thanks for the patch. > And thanks to Jason for spotting the issue. And for coping with my initial inability to parse his report! Thanks, tglx
WARNING: multiple messages have this Message-ID (diff)
From: tglx@linutronix.de (Thomas Gleixner) To: linux-arm-kernel@lists.infradead.org Subject: too many timer retries happen when do local timer swtich with broadcast timer Date: Thu, 21 Feb 2013 23:19:18 +0100 (CET) [thread overview] Message-ID: <alpine.LFD.2.02.1302212214020.22263@ionos> (raw) In-Reply-To: <51263975.20906@ti.com> 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. > Tested-by: Santosh Shilimkar <santosh.shilimkar@ti.com> > > Thanks for the patch. > And thanks to Jason for spotting the issue. And for coping with my initial inability to parse his report! Thanks, tglx
next prev parent reply other threads:[~2013-02-21 22:19 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 [this message] 2013-02-21 22:19 ` Thomas Gleixner 2013-02-22 10:07 ` Santosh Shilimkar 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=alpine.LFD.2.02.1302212214020.22263@ionos \ --to=tglx@linutronix.de \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=liu.h.jason@gmail.com \ --cc=santosh.shilimkar@ti.com \ /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: linkBe 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.