linux-kernel - Will CPU 0 be forever prohibited from NO_HZ

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-next>] [day] [month] [year] [list]

Message-ID: <20131204193957.GA2847@linux.vnet.ibm.com>
Date:	Wed, 4 Dec 2013 11:39:57 -0800
From:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:	fweisbec@...il.com
Cc:	linux-kernel@...r.kernel.org
Subject: Will CPU 0 be forever prohibited from NO_HZ_FULL status?

Hello, Frederic,

Just realized that I could further decrease RT latency of one of my "shut
up RCU on NO_HZ_FULL CPUs" patches if I relied on CPU 0 always having
a scheduling-clock tick unless the entire system is idle.  The trick
is that I could then rely on CPU 0 to detect RCU CPU stall warnings,
and remove the checking from the other CPUs.

Thoughts?

							Thanx, Paul

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