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: Tue, 21 Dec 2010 00:37:04 +0100 From: Frederic Weisbecker <fweisbec@...il.com> To: Peter Zijlstra <a.p.zijlstra@...llo.nl> Cc: LKML <linux-kernel@...r.kernel.org>, Thomas Gleixner <tglx@...utronix.de>, "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>, Ingo Molnar <mingo@...e.hu>, Steven Rostedt <rostedt@...dmis.org>, Lai Jiangshan <laijs@...fujitsu.com>, Andrew Morton <akpm@...ux-foundation.org>, Anton Blanchard <anton@....ibm.com>, Tim Pepper <lnxninja@...ux.vnet.ibm.com> Subject: Re: [RFC PATCH 04/15] nohz_task: Stop the tick when the nohz task runs alone On Mon, Dec 20, 2010 at 04:51:39PM +0100, Peter Zijlstra wrote: > On Mon, 2010-12-20 at 16:24 +0100, Frederic Weisbecker wrote: > > Check from the timer interrupt that we are a nohz task running > > alone in the CPU and stop the tick if this is the case. > > > Does this verify that the tick has no other work to do? > > I see no list of things the tick does and a checklist that everything it > does is indeed superfluous. In a subsequent patch we check if rcu also needs the tick. For the rest, tick_nohz_stop_sched_tick() knows what to do: keep the next tick or switch to nohz. Hm? -- 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