[Top] [All Lists]

[xfs-masters] Re: Linux 2.6.17-rc2 - notifier chain problem?

To: Chandra Seetharaman <sekharan@xxxxxxxxxx>
Subject: [xfs-masters] Re: Linux 2.6.17-rc2 - notifier chain problem?
From: Ashok Raj <ashok.raj@xxxxxxxxx>
Date: Wed, 26 Apr 2006 13:26:45 -0700
Cc: Ashok Raj <ashok.raj@xxxxxxxxx>, Andrew Morton <akpm@xxxxxxxx>, Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>, herbert@xxxxxxxxxxxx, torvalds@xxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, linux-xfs@xxxxxxxxxxx, xfs-masters@xxxxxxxxxxx
In-reply-to: <1146082893.24650.27.camel@linuxchandra>; from sekharan@xxxxxxxxxx on Wed, Apr 26, 2006 at 01:21:33PM -0700
References: <Pine.LNX.4.44L0.0604261144010.6376-100000@xxxxxxxxxxxxxxxxxxxx> <1146075534.24650.11.camel@linuxchandra> <20060426114348.51e8e978.akpm@xxxxxxxx> <20060426122926.A31482@xxxxxxxxxxxxxxxxxxxx> <1146082893.24650.27.camel@linuxchandra>
Reply-to: xfs-masters@xxxxxxxxxxx
Sender: xfs-masters-bounce@xxxxxxxxxxx
Trustinternalsourcedmail: True
User-agent: Mutt/
On Wed, Apr 26, 2006 at 01:21:33PM -0700, Chandra Seetharaman wrote:
> > 
> > The problem we ran into was some of the startup code depends on the notifier
> > call chain for smp bringup, hence we couldn't nuke it similar to 
> > hotcpu_notifier().
> I do not understand the problem. If everybody that uses
> register_cpu_notifier() starts using __cpuinit and __cpuinitdata (or the
> devinit siblings), then the notifier mechanism will not be any different
> than what they are now, right ? (both in hotplug cpu and non-hotplug cpu
> case) Or am i missing something ?

Well, register_cpu_notifier() is an exported function. There are several 
modules that use this today like cpufreq etc which disqualifies it to be
a init style function.

either that function should be devinit and be present premanently, or
should be mapped to null macro for correctness.

Otherwise module loaders will start to oops when they call into 

Ashok Raj
- Open Source Technology Center

<Prev in Thread] Current Thread [Next in Thread>