From: Ingo Molnar <mingo@elte.hu>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
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>
Subject: Re: [PATCH RFC V3 2/8] stop_machine: make stop_machine safe and efficient to call early
Date: Mon, 10 Oct 2011 09:34:05 +0200 [thread overview]
Message-ID: <20111010073405.GC29035@elte.hu> (raw)
In-Reply-To: <8762k4grwy.fsf@rustcorp.com.au>
* 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?
Thanks,
Ingo
next prev parent reply other threads:[~2011-10-10 7:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-04 19:18 [PATCH RFC V3 0/8] jump-label: allow early jump_label_enable() Jeremy Fitzhardinge
2011-10-04 19:18 ` [PATCH RFC V3 1/8] jump_label: use proper atomic_t initializer Jeremy Fitzhardinge
2011-10-04 19:18 ` [PATCH RFC V3 2/8] stop_machine: make stop_machine safe and efficient to call early Jeremy Fitzhardinge
2011-10-05 1:15 ` Rusty Russell
2011-10-10 7:34 ` Ingo Molnar [this message]
2011-10-10 20:01 ` Jeremy Fitzhardinge
2011-10-12 7:34 ` Ingo Molnar
2011-10-12 7:45 ` Peter Zijlstra
2011-10-12 15:44 ` Jeremy Fitzhardinge
2011-10-04 19:18 ` [PATCH RFC V3 3/8] jump_label: if a key has already been initialized, don't nop it out Jeremy Fitzhardinge
2011-10-04 19:18 ` [PATCH RFC V3 4/8] x86/jump_label: drop arch_jump_label_text_poke_early() Jeremy Fitzhardinge
2011-10-04 19:18 ` [PATCH RFC V3 5/8] sparc/jump_label: " Jeremy Fitzhardinge
2011-10-04 19:18 ` [PATCH RFC V3 6/8] jump_label: add arch_jump_label_transform_static() to optimise non-live code updates Jeremy Fitzhardinge
2011-10-04 19:18 ` [PATCH RFC V3 7/8] s390/jump-label: add arch_jump_label_transform_static() Jeremy Fitzhardinge
2011-10-04 19:18 ` [PATCH RFC V3 8/8] x86/jump_label: " Jeremy Fitzhardinge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111010073405.GC29035@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=david.daney@cavium.com \
--cc=hpa@linux.intel.com \
--cc=jang@linux.vnet.ibm.com \
--cc=jbaron@redhat.com \
--cc=jeremy.fitzhardinge@citrix.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@ellerman.id.au \
--cc=rostedt@goodmis.org \
--cc=rusty@rustcorp.com.au \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome