linux-kernel - Re: [PATCH 06/10] nohz: Define meaningful symbol for nohz full timekeeper

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 25 Jul 2014 23:27:07 +0200
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...nel.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Viresh Kumar <viresh.kumar@...aro.org>
Subject: Re: [PATCH 06/10] nohz: Define meaningful symbol for nohz full
 timekeeper

On Mon, Jul 21, 2014 at 11:12:55AM -0700, Paul E. McKenney wrote:
> On Sat, Jul 19, 2014 at 02:44:17AM +0200, Frederic Weisbecker wrote:
> > The nohz full timekeeper is always CPU 0. Lets add it to the list of
> > special tick_do_timer_cpu symbols for more self explanatory code.
> > 
> > Cc: Ingo Molnar <mingo@...nel.org>
> > Cc: Paul E. McKenney <paulmck@...ux.vnet.ibm.com>
> > Cc: Peter Zijlstra <peterz@...radead.org>
> > Cc: Steven Rostedt <rostedt@...dmis.org>
> > Cc: Thomas Gleixner <tglx@...utronix.de>
> > Cc: Viresh Kumar <viresh.kumar@...aro.org>
> > Signed-off-by: Frederic Weisbecker <fweisbec@...il.com>
> 
> Sounds like Nicolas Pitre would like to be able to specify the default,
> perhaps at build time, but aside from that requested enhancement:

Ok. That's outside the scope of this patchset though as it doesn't change much things
in this regard: CPU 0 has been the timekeeper since the early days of nohz full.
And we still need a default timekeeper in any case, whether we can override it or not
in the future. So we still need that patch.

Then if big.LITTLE people are really interested in nohz full, we can still enhance
that in the future.

Thanks!
--
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/