public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu,
	akpm@linux-foundation.org, hch@infradead.org, mmlnx@us.ibm.com,
	dipankar@in.ibm.com, dsmith@redhat.com, rostedt@goodmis.org,
	adrian.bunk@movial.fi, a.p.zijlstra@chello.nl, ego@in.ibm.com,
	niv@us.ibm.com, dvhltc@us.ibm.com, rusty@au1.ibm.com,
	jkenisto@linux.vnet.ibm.com, oleg@tv-sign.ru
Subject: Re: [PATCH,RFC] Initialize call_rcu_sched sooner
Date: Tue, 25 Mar 2008 11:49:12 -0700	[thread overview]
Message-ID: <20080325184912.GL4555@linux.vnet.ibm.com> (raw)
In-Reply-To: <20080325125308.GA19690@Krystal>

On Tue, Mar 25, 2008 at 08:53:08AM -0400, Mathieu Desnoyers wrote:
> Initialize call_rcu_sched sooner so it can be used in module_init stage.
> 
> (needed for LTTng)

This passes smoke tests, so have incorporated it.  Thank you, Mathieu!!!

						Thanx, Paul

> Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
> ---
>  init/main.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> Index: linux-2.6-lttng/init/main.c
> ===================================================================
> --- linux-2.6-lttng.orig/init/main.c	2008-03-25 08:49:02.000000000 -0400
> +++ linux-2.6-lttng/init/main.c	2008-03-25 08:49:20.000000000 -0400
> @@ -738,13 +738,13 @@ static void __init do_initcalls(void)
>   */
>  static void __init do_basic_setup(void)
>  {
> +	rcu_init_sched();
>  	/* drivers will send hotplug events */
>  	init_workqueues();
>  	usermodehelper_init();
>  	driver_init();
>  	init_irq_proc();
>  	do_initcalls();
> -	rcu_init_sched();
>  }
> 
>  static int __initdata nosoftlockup;
> -- 
> Mathieu Desnoyers
> Computer Engineering Ph.D. Student, Ecole Polytechnique de Montreal
> OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68

  reply	other threads:[~2008-03-25 18:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-21 14:36 [PATCH,RFC] Add call_rcu_sched() Paul E. McKenney
2008-03-21 22:40 ` Paul E. McKenney
2008-03-24  5:06   ` Mathieu Desnoyers
2008-03-24  5:46     ` Paul E. McKenney
2008-03-24 13:59       ` Mathieu Desnoyers
2008-03-25 12:53       ` [PATCH,RFC] Initialize call_rcu_sched sooner Mathieu Desnoyers
2008-03-25 18:49         ` Paul E. McKenney [this message]
2008-04-06 21:37   ` [PATCH,RFC] Add call_rcu_sched() Paul E. McKenney
2008-04-08  7:34     ` Andrew Morton
2008-04-08  8:10       ` Gautham R Shenoy
2008-04-08  8:39         ` Andrew Morton
2008-04-08  8:56           ` Gautham R Shenoy
2008-04-08  9:07             ` Andrew Morton
2008-04-08 17:17               ` Paul E. McKenney
2008-04-08 16:59       ` Paul E. McKenney

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=20080325184912.GL4555@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=adrian.bunk@movial.fi \
    --cc=akpm@linux-foundation.org \
    --cc=dipankar@in.ibm.com \
    --cc=dsmith@redhat.com \
    --cc=dvhltc@us.ibm.com \
    --cc=ego@in.ibm.com \
    --cc=hch@infradead.org \
    --cc=jkenisto@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@polymtl.ca \
    --cc=mingo@elte.hu \
    --cc=mmlnx@us.ibm.com \
    --cc=niv@us.ibm.com \
    --cc=oleg@tv-sign.ru \
    --cc=rostedt@goodmis.org \
    --cc=rusty@au1.ibm.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