| 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
| ||
|
Date: Thu, 2 Jun 2011 12:18:35 +0200 From: Mattias Wallin <mattias.wallin@...ricsson.com> To: Russell King - ARM Linux <linux@....linux.org.uk> Cc: Thomas Gleixner <tglx@...utronix.de>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>, Lee Jones <lee.jones@...aro.org> Subject: Re: [PATCHv2 0/3] clocksource: add db8500 PRCMU timer On 06/02/2011 11:46 AM, Russell King - ARM Linux wrote: > Why don't we just find a way of fixing sched_clock so that the value > doesn't reset over a suspend/resume cycle? Even if the value isn't reset during suspend/resume we want the clocksource to keep counting. Or is it ok to have the clocksource stop or freeze during suspend? Then we have cpuidle. Is it ok to stop/freeze the timer during cpuidle sleep states? My view is that sched_clock and the clocksource read should return the time since boot and keep counting during sleep and suspend. (In this case we use the same timer for both sched_clk and clocksource.) > IOW, lets fix the problem > for_everyone_ rather than only fixing it for one platform at a time. I agree that fixing it for everyone would be better and I can give it a try if I get pointed in the right direction. -- 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/
Powered by blists - more mailing lists