linux-kernel - Re: <PING> Re: [patch x86/core] x86: allow number of additional hotplug CPUs to be set at compile time

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: <20081005155614.GA5356@elte.hu>
Date:	Sun, 5 Oct 2008 17:56:14 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	Chuck Ebbert <cebbert@...hat.com>,
	Andi Kleen <andi@...stfloor.org>, linux-kernel@...r.kernel.org,
	Arjan van de Ven <arjan@...radead.org>
Subject: Re: <PING> Re: [patch x86/core] x86: allow number of additional
	hotplug CPUs to be set at compile time


* Thomas Gleixner <tglx@...utronix.de> wrote:

> > and no way can any of this go into v2.6.27: this is fragile code 
> > with a lot of historic baggage and the original error is non-fatal 
> > to begin with. It can easily be backported to .27.1 if testing shows 
> > that it has no other adverse side-effects.
> 
> Please lets get rid of all this.
> 
> Thanks,
> 
> 	tglx
> ---------------->
> >From 344707c1f43dd0d080828497aacb60c0cc0a8c13 Mon Sep 17 00:00:00 2001
> From: Thomas Gleixner <tglx@...utronix.de>
> Date: Sun, 5 Oct 2008 17:27:56 +0200
> Subject: [PATCH] x86, smpboot: remove additional_cpus
> 
> remove remainder of additional_cpus logic. We now just listen to the
> disabled_cpus value like we did for years. disabled_cpus is always >=
> 0 so no need for an extra check.
>
> Signed-off-by: Thomas Gleixner <tglx@...utronix.de>

applied to tip/x86/core - thanks Thomas!

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