From: Rusty Russell Subject: Re: [PATCH RFC V3 2/8] stop_machine: make stop_machine safe and efficient to call early Date: Wed, 05 Oct 2011 11:45:25 +1030 Message-ID: <8762k4grwy.fsf@rustcorp.com.au> References: <619c66d6da63aa086e2eac017e7aed216cc8ddc3.1317755691.git.jeremy.fitzhardinge@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: In-Reply-To: <619c66d6da63aa086e2eac017e7aed216cc8ddc3.1317755691.git.jeremy.fitzhardinge@citrix.com> Sender: linux-kernel-owner@vger.kernel.org To: Jeremy Fitzhardinge , Steven Rostedt Cc: "David S. Miller" , David Daney , Michael Ellerman , Jan Glauber , Jason Baron , the arch/x86 maintainers , Xen Devel , Linux Kernel Mailing List , Jeremy Fitzhardinge , Peter Zijlstra , Andrew Morton , "H. Peter Anvin" , Ingo Molnar List-Id: xen-devel@lists.xenproject.org On Tue, 4 Oct 2011 12:18:03 -0700, Jeremy Fitzhardinge wrote: > From: Jeremy Fitzhardinge > > 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 Cheers, Rusty.