linux-kernel - Re: [patch 00/18] SMP: Boot and CPU hotplug refactoring

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: <alpine.LFD.2.02.1204201618320.2542@ionos>
Date:	Fri, 20 Apr 2012 16:19:09 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	richard -rw- weinberger <richard.weinberger@...il.com>
cc:	LKML <linux-kernel@...r.kernel.org>, linux-arch@...r.kernel.org,
	Peter Zijlstra <peterz@...radead.org>,
	Rusty Russell <rusty@...tcorp.com.au>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Ingo Molnar <mingo@...nel.org>,
	"Srivatsa S. Bhat" <srivatsa.bhat@...ux.vnet.ibm.com>
Subject: Re: [patch 00/18] SMP: Boot and CPU hotplug refactoring - Part 1

On Fri, 20 Apr 2012, richard -rw- weinberger wrote:

> On Fri, Apr 20, 2012 at 3:05 PM, Thomas Gleixner <tglx@...utronix.de> wrote:
> > This converts all architectures except m32r, mn10300, tile and UM to
> > the new core facility. These architecture are calling fork_idle() in
> > the very early boot code in smp_prepare_cpus() for unknown reasons.
> > I haven't analyzed yet, whether this is on purpose or can be moved
> > over to the generic facility. It'd be nice if the responsible maintainers
> > could look into that as well.
> 
> SMP is marked as broken on UM, so I don't have any objections. :-)

Great. So we can break it some more and let the poor sod who tries to
fix UM SMP deal with it :)

Thanks,

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