[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160518133529.GH3193@twins.programming.kicks-ass.net>
Date: Wed, 18 May 2016 15:35:29 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Chris Metcalf <cmetcalf@...lanox.com>
Cc: Gilad Ben Yossef <giladb@...hip.com>,
Steven Rostedt <rostedt@...dmis.org>,
Ingo Molnar <mingo@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Rik van Riel <riel@...hat.com>, Tejun Heo <tj@...nel.org>,
Frederic Weisbecker <fweisbec@...il.com>,
Thomas Gleixner <tglx@...utronix.de>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Christoph Lameter <cl@...ux.com>,
Viresh Kumar <viresh.kumar@...aro.org>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will.deacon@....com>,
Andy Lutomirski <luto@...capital.net>,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v12 05/13] task_isolation: support
CONFIG_TASK_ISOLATION_ALL
On Tue, Apr 05, 2016 at 01:38:34PM -0400, Chris Metcalf wrote:
> This option, similar to NO_HZ_FULL_ALL, simplifies configuring
> a system to boot by default with all cores except the boot core
> running in task isolation mode.
Hurm, we still have that option? I thought we killed it, because random
people set it and 'complain' their system misbehaves.
Powered by blists - more mailing lists