From: Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH RFC V3 2/8] stop_machine: make stop_machine safe and
 efficient to call early
Date: Wed, 12 Oct 2011 09:34:03 +0200
Message-ID: <20111012073402.GJ18618@elte.hu>
References: <cover.1317755691.git.jeremy.fitzhardinge@citrix.com>
 <619c66d6da63aa086e2eac017e7aed216cc8ddc3.1317755691.git.jeremy.fitzhardinge@citrix.com>
 <8762k4grwy.fsf@rustcorp.com.au>
 <20111010073405.GC29035@elte.hu>
 <4E934F37.2020300@goop.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <linux-kernel-owner@vger.kernel.org>
Content-Disposition: inline
In-Reply-To: <4E934F37.2020300@goop.org>
Sender: linux-kernel-owner@vger.kernel.org
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>, Steven Rostedt <rostedt@goodmis.org>, "David S. Miller" <davem@davemloft.net>, David Daney <david.daney@cavium.com>, Michael Ellerman <michael@ellerman.id.au>, Jan Glauber <jang@linux.vnet.ibm.com>, Jason Baron <jbaron@redhat.com>, the arch/x86 maintainers <x86@kernel.org>, Xen Devel <xen-devel@lists.xensource.com>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>, Peter Zijlstra <a.p.zijlstra@chello.nl>, Andrew Morton <akpm@linux-foundation.org>, "H. Peter Anvin" <hpa@linux.intel.com>
List-Id: xen-devel@lists.xenproject.org


* Jeremy Fitzhardinge <jeremy@goop.org> wrote:

> On 10/10/2011 12:34 AM, Ingo Molnar wrote:
> > * Rusty Russell <rusty@rustcorp.com.au> wrote:
> >
> >> On Tue,  4 Oct 2011 12:18:03 -0700, Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> >>> From: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
> >>>
> >>> Make stop_machine() safe to call early in boot, before stop_machine()
> >>> has been set up, by simply calling the callback function directly if
> >>> there's only one CPU online.
> >> Not that you need this, since it's >90% Tejun's code now, but:
> >>
> >> Acked-by: Rusty Russell <rusty@rustcorp.com.au>
> > hey, extra review is always useful.
> >
> > Jeremy, Tejun, what's the expected merge path of these changes?
> 
> Andrew has already picked up the stop_machine patch, I think.  But it's
> pretty settled now, so it shouldn't cause any problem if it gets via
> multiple paths.
> 
> What about the jump-label stuff?  Has that been going via tip.git in the
> past, or by some other path?

If it has Jason's and PeterZ's ack then it can go via any other tree 
in this cycle - we are not carrying jump label patches right now.

But those acks are very much desired.

Thanks,

	Ingo