linux-kernel - Re: [PATCH] arm: sched: stop sched

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 23 Oct 2012 00:28:32 +0200
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Kevin Hilman <khilman@...prootsystems.com>,
	John Stultz <john.stultz@...aro.org>,
	Thomas Gleixner <tglx@...utronix.de>
Cc:	Felipe Balbi <balbi@...com>,
	Russell King <rmk+kernel@....linux.org.uk>,
	Linux ARM Kernel Mailing List 
	<linux-arm-kernel@...ts.infradead.org>,
	Linux OMAP Mailing List <linux-omap@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Paul Walmsley <paul@...an.com>,
	Tony Lindgren <tony@...mide.com>,
	Santosh Shilimkar <santosh.shilimkar@...com>,
	Andrew Lunn <andrew@...n.ch>,
	Daniel Walker <dwalker@...o99.com>,
	Lennert Buytenhek <kernel@...tstofly.org>,
	Kukjin Kim <kgene.kim@...sung.com>,
	Bryan Huntsman <bryanh@...eaurora.org>,
	David Brown <davidb@...eaurora.org>,
	Arnd Bergmann <arnd@...db.de>,
	Stephen Warren <swarren@...dotorg.org>,
	Ben Dooks <ben-linux@...ff.org>,
	Alexander Schulz <alex@...rk-linux.de>,
	Andrew Victor <linux@...im.org.za>,
	Kyungmin Park <kyungmin.park@...sung.com>,
	Sascha Hauer <kernel@...gutronix.de>,
	Olof Johansson <olof@...om.net>,
	Colin Cross <ccross@...roid.com>,
	Barry Song <21cnbao@...il.com>
Subject: Re: [PATCH] arm: sched: stop sched_clock() during suspend

On Mon, Oct 22, 2012 at 7:05 PM, Kevin Hilman
<khilman@...prootsystems.com> 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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/