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 02:40:21 +0100 From: Frederic Weisbecker <fweisbec@...il.com> To: Peter Zijlstra <a.p.zijlstra@...llo.nl>, Thomas Gleixner <tglx@...utronix.de> Cc: LKML <linux-kernel@...r.kernel.org>, "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 12/15] clocksource: Ignore nohz task cpu in clocksource watchdog On Mon, Dec 20, 2010 at 05:27:38PM +0100, Peter Zijlstra wrote: > On Mon, 2010-12-20 at 16:24 +0100, Frederic Weisbecker wrote: > > > > The watchdog should probably make an exception for nohz task cpus > > that want to be interrupted the least possible. > > > > However we probably need to warn the user about that. > > > > Another solution would be to make this timer defferable. > > Nah, both skipping a cpu and making the timer deferrable render the > watchdog useless, just disable the thing. Thomas seemed to prefer we keep it but just ignore the nohz task cpus I mean when we talked about that at that time, the notion of nohz was purely per cpu. Now we wish the notion of nohz task cpu could disappear, so we should indeed deactivate the thing for that config. Would be nice to have Thomas opinion too. -- 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