linux-kernel - Re: [patch 2/4] introduce the mechanism of disabling cpu hotplug control

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

Message-Id: <20061107203504.b8e17ea8.akpm@osdl.org>
Date:	Tue, 7 Nov 2006 20:35:04 -0800
From:	Andrew Morton <akpm@...l.org>
To:	"Siddha, Suresh B" <suresh.b.siddha@...el.com>
Cc:	ak@...e.de, shaohua.li@...el.com, linux-kernel@...r.kernel.org,
	discuss@...-64.org, ashok.raj@...el.com
Subject: Re: [patch 2/4] introduce the mechanism of disabling cpu hotplug
 control

On Tue, 7 Nov 2006 20:01:34 -0800
"Siddha, Suresh B" <suresh.b.siddha@...el.com> wrote:

> I wanted to add something like disable_cpu_hotplug

My point is, `enable_cpu_hotplug' is nicer

	if (enable_cpu_hotplug)
		...
	if (!enable_cpu_hotplug)
		...

versus

	if (disable_cpu_hotplug)
		...
	if (!disable_cpu_hotplug)
		...			/* My brain hurts */



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