From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Hilman Subject: Re: [PATCH] arm: sched: stop sched_clock() during suspend Date: Tue, 23 Oct 2012 07:17:33 -0700 Message-ID: <87a9vdclxe.fsf@deeprootsystems.com> References: <1350906877-19410-1-git-send-email-balbi@ti.com> <873916h1yi.fsf@deeprootsystems.com> <20121023092231.GE28061@n2100.arm.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20121023092231.GE28061@n2100.arm.linux.org.uk> (Russell King's message of "Tue, 23 Oct 2012 10:22:31 +0100") List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-arm-kernel-bounces@lists.infradead.org Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Russell King - ARM Linux Cc: Andrew Lunn , Tony Lindgren , Linus Walleij , Daniel Walker , Thomas Gleixner , Kukjin Kim , Barry Song <21cnbao@gmail.com>, Kyungmin Park , Lennert Buytenhek , David Brown , Arnd Bergmann , Stephen Warren , John Stultz , Ben Dooks , Alexander Schulz , Linux OMAP Mailing List , Andrew Victor , Linux ARM Kernel Mailing List , Paul Walmsley , Linux Kernel Mailing List , Felipe Balbi , Bryan Huntsman , Santosh List-Id: linux-omap@vger.kernel.org Russell King - ARM Linux writes: > On Tue, Oct 23, 2012 at 12:28:32AM +0200, Linus Walleij wrote: >> On Mon, Oct 22, 2012 at 7:05 PM, Kevin Hilman >> wrote: >> >> > However, in light of RT throttling, this a correctness issue for process >> > accounting, so I agree that this should be done for all platforms >> > instead of providing an optional 'needs suspend' version of the API, >> > even though it means printk times no longer reflect time spent >> > suspended. >> >> Maybe we should get printk() to use the best clocksource >> instead. >> >> The reason AFAICT that printk() is using sched_clock() is that >> it's supposed to be fast. But now it seems that it's not going >> to return what printk() needs anymore. > > No, printk() does not need this. You think it does, but it doesn't. What > we have is a difference between ARM and x86, and this difference is breaking > the scheduler. > > The fact that the printk timestamp increments while suspended is a bug. It > doesn't on x86. Russell, I agree that it's a bug, but does it qualify as a something you're willing to take for v3.7-rc? For OMAP, we need to know if this will go for v3.7 or not because there's a regression in the OMAP I2C driver, and if this doesn't go in, we'll need to revert something in the I2C driver until it does. Thanks, Kevin