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: Mon, 9 Nov 2015 16:21:22 -0800 From: Jacob Pan <jacob.jun.pan@...ux.intel.com> To: Peter Zijlstra <peterz@...radead.org>, LKML <linux-kernel@...r.kernel.org> Cc: Rafael Wysocki <rafael.j.wysocki@...el.com>, Len Brown <len.brown@...el.com>, Andi Kleen <andi.kleen@...el.com>, Thomas Gleixner <tglx@...utronix.de>, Paul Turner <pjt@...gle.com>, Tim Chen <tim.c.chen@...ux.intel.com>, Dietmar Eggemann <dietmar.eggemann@....com>, Eduardo Valentin <edubezval@...il.com>, Punit Agrawal <punit.agrawal@....com>, Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>, Jacob Pan <jacob.jun.pan@...ux.intel.com> Subject: [RFC PATCH v2 2/3] timer: relax tick stop in idle entry Upon entering idle, we can turn off tick if the next timeout is exactly one tick away. Otherwise, we could enter inner idle loop with tick still enabled, without resched set, the tick will continue during idle therefore less optimal in terms of energy savings. Signed-off-by: Jacob Pan <jacob.jun.pan@...ux.intel.com> --- kernel/time/tick-sched.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/time/tick-sched.c b/kernel/time/tick-sched.c index 7c7ec45..bcadaab 100644 --- a/kernel/time/tick-sched.c +++ b/kernel/time/tick-sched.c @@ -606,7 +606,7 @@ static ktime_t tick_nohz_stop_sched_tick(struct tick_sched *ts, * restart it proper. */ delta = next_tick - basemono; - if (delta <= (u64)TICK_NSEC) { + if (delta < (u64)TICK_NSEC) { tick.tv64 = 0; if (!ts->tick_stopped) goto out; -- 1.9.1 -- 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