[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1360255280.2621.70.camel@gandalf.local.home>
Date: Thu, 07 Feb 2013 11:41:20 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Frederic Weisbecker <fweisbec@...il.com>
Cc: Ingo Molnar <mingo@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
Alessio Igor Bogani <abogani@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Chris Metcalf <cmetcalf@...era.com>,
Christoph Lameter <cl@...ux.com>,
Geoff Levand <geoff@...radead.org>,
Gilad Ben Yossef <gilad@...yossef.com>,
Hakan Akkan <hakanakkan@...il.com>,
Li Zhong <zhong@...ux.vnet.ibm.com>,
Namhyung Kim <namhyung.kim@....com>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Paul Gortmaker <paul.gortmaker@...driver.com>,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [ANNOUNCE] 3.8-rc6-nohz4
On Thu, 2013-02-07 at 17:25 +0100, Frederic Weisbecker wrote:
> At least for now we seem to agree on CONFIG_NO_HZ_IDLE and keep
> CONFIG_NO_HZ for compatibility. Are you ok with that? If so I'll send
> a patch.
I believe that Ingo was suggesting to have CONFIG_NO_HZ give options to
what type of config NO_HZ you want. Something like:
config NO_HZ
bool "Enable tickless support"
config NO_HZ_IDLE
bool "Stop tick when CPU is idle"
default y
depends on NO_HZ
config NO_HZ_TASK
bool "Stop tick on specified CPUs when single task is running"
default n
depends on NO_HZ
That is, if you select NO_HZ, by default NO_HZ_IDLE is also selected.
But in the kernel the NO_HZ_IDLE is used.
-- Steve
--
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