From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755915Ab1JMSQx (ORCPT ); Thu, 13 Oct 2011 14:16:53 -0400 Received: from claw.goop.org ([74.207.240.146]:49927 "EHLO claw.goop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755841Ab1JMSQv (ORCPT ); Thu, 13 Oct 2011 14:16:51 -0400 Message-ID: <4E97184D.8020109@goop.org> Date: Thu, 13 Oct 2011 09:56:45 -0700 From: Jeremy Fitzhardinge User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20110930 Thunderbird/7.0.1 MIME-Version: 1.0 To: Peter Zijlstra CC: Steven Rostedt , "David S. Miller" , David Daney , Michael Ellerman , Jan Glauber , Jason Baron , the arch/x86 maintainers , Xen Devel , Linux Kernel Mailing List , Ingo Molnar , "H. Peter Anvin" , Jeremy Fitzhardinge Subject: Re: [PATCH RFC V4 10/10] jump-label: initialize jump-label subsystem much earlier References: <1318502628.24856.10.camel@twins> In-Reply-To: <1318502628.24856.10.camel@twins> X-Enigmail-Version: 1.3.2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/13/2011 03:43 AM, Peter Zijlstra wrote: > On Wed, 2011-10-12 at 17:08 -0700, Jeremy Fitzhardinge wrote: >> From: Jeremy Fitzhardinge >> >> Initialize jump_labels much earlier, we can use them. > We can use them, where? how? what?, that sentence just begs for more. Er, yeah, looks like I committed it without actually finishing the sentence. J >> diff --git a/init/main.c b/init/main.c >> index 2a9b88a..f4094ed 100644 >> --- a/init/main.c >> +++ b/init/main.c >> @@ -637,6 +637,7 @@ asmlinkage void __init start_kernel(void) >> acpi_early_init(); /* before LAPIC and SMP init */ >> sfi_init_late(); >> >> + jump_label_init(); >> ftrace_init(); >> >> /* Do the rest non-__init'ed, we're now alive */ > Can we push them much earlier still? If possible I'd like them to be > before sched_init() so that I might use them there, if not possible, at > the very least before enabling interrupts would be nice. > >