Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932344Ab2JVW2f (ORCPT ); Mon, 22 Oct 2012 18:28:35 -0400 Received: from mail-wi0-f178.google.com ([209.85.212.178]:52168 "EHLO mail-wi0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932281Ab2JVW2e (ORCPT ); Mon, 22 Oct 2012 18:28:34 -0400 MIME-Version: 1.0 In-Reply-To: <873916h1yi.fsf@deeprootsystems.com> References: <1350906877-19410-1-git-send-email-balbi@ti.com> <873916h1yi.fsf@deeprootsystems.com> Date: Tue, 23 Oct 2012 00:28:32 +0200 Message-ID: Subject: Re: [PATCH] arm: sched: stop sched_clock() during suspend From: Linus Walleij To: Kevin Hilman , John Stultz , Thomas Gleixner Cc: Felipe Balbi , Russell King , Linux ARM Kernel Mailing List , Linux OMAP Mailing List , Linux Kernel Mailing List , Paul Walmsley , Tony Lindgren , Santosh Shilimkar , Andrew Lunn , Daniel Walker , Lennert Buytenhek , Kukjin Kim , Bryan Huntsman , David Brown , Arnd Bergmann , Stephen Warren , Ben Dooks , Alexander Schulz , Andrew Victor , Kyungmin Park , Sascha Hauer , Olof Johansson , Colin Cross , Barry Song <21cnbao@gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 919 Lines: 25 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. (Dragging Stultz & Gleixner into this...) Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/