linux-kernel - Re: [ANNOUNCE] Full dynticks selftests 0.0.1

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 for Android: free password hash cracker in your pocket

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

Message-ID: <0000013f5ccd9d66-616fef8f-7cf1-45ec-bd20-b1fed9264cbe-000000@email.amazonses.com>
Date:	Wed, 19 Jun 2013 14:19:06 +0000
From:	Christoph Lameter <cl@...two.org>
To:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
cc:	Frederic Weisbecker <fweisbec@...il.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	Ingo Molnar <mingo@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Peter Zijlstra <peterz@...radead.org>,
	Li Zhong <zhong@...ux.vnet.ibm.com>,
	Borislav Petkov <bp@...en8.de>,
	Kevin Hilman <khilman@...aro.org>,
	Mats Liljegren <liljegren.mats2@...il.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [ANNOUNCE] Full dynticks selftests 0.0.1

On Tue, 18 Jun 2013, Paul E. McKenney wrote:

> +online to handle timekeeping tasks in order to ensure that system
> +calls like gettimeofday() returns accurate values on adaptive-tick CPUs.
> +(This is not an issue for CONFIG_NO_HZ_IDLE=y because there are no running
> +user processes to observe slight drifts in clock rate.)  Therefore, the
> +boot CPU is prohibited from entering adaptive-ticks mode.  Specifying a
> +"nohz_full=" mask that includes the boot CPU will result in a boot-time
> +error message, and the boot CPU will be removed from the mask.  Note that
> +this means that your system must have at least two CPUs in order for
> +CONFIG_NO_HZ_FULL=y to do anything for you.

These are some important point here. Very good. 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/