[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1332419558.2487.14.camel@twins>
Date: Thu, 22 Mar 2012 13:32:38 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: "Srivatsa S. Bhat" <srivatsa.bhat@...ux.vnet.ibm.com>
Cc: rkuo@...eaurora.org, tglx@...utronix.de, linas@...eaurora.org,
mingo@...e.hu, dhowells@...hat.com,
yasutake.koichi@...panasonic.com, akpm@...ux-foundation.org,
benh@...nel.crashing.org, jesper.nilsson@...s.com,
cmetcalf@...era.com, linux@....linux.org.uk, jejb@...isc-linux.org,
deller@....de, vapier@...too.org, linux-hexagon@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-am33-list@...hat.com,
linux-parisc@...r.kernel.org
Subject: Re: [PATCH 0/4] arch/CPU hotplug: Add missing CPU Hotplug bits to
fix nasty issues
On Thu, 2012-03-22 at 13:13 +0100, Peter Zijlstra wrote:
>
> Furthermore, I was pondering the scenario where a 3rd cpu IPIs the newly
> booting cpu, I suspect we need a smp_wmb() after setting cpu_active and
> a rmb in select_fallback_rq() before reading active.
Hmm, not IPI, that would be covered by the disabling of interrupts on
bringup, but somehow manage to wake a thread that's strictly affine that
the fresh cpu, like queue_work_on() or so.
--
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/
Powered by blists - more mailing lists