linux-mips
[Top] [All Lists]

Re: OProfile cannot be loaded as module...

To: David Daney <ddaney@avtrex.com>
Subject: Re: OProfile cannot be loaded as module...
From: Ralf Baechle <ralf@linux-mips.org>
Date: Tue, 18 Oct 2005 17:38:48 +0100
Cc: linux-mips@linux-mips.org
In-reply-to: <435518CC.3060403@avtrex.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <43470BCF.1070709@avtrex.com> <20051013225520.GA3234@linux-mips.org> <43540609.4000105@avtrex.com> <20051018110355.GB2656@linux-mips.org> <435518CC.3060403@avtrex.com>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.4.2.1i
On Tue, Oct 18, 2005 at 08:46:20AM -0700, David Daney wrote:

> Given your 'yes' and 'no' answers, the behavior of a module could depend 
> on the order in which the modules are loaded, as they can be linked 
> differently depending on which modules are already present.
> 
> That doesn't seem like a good way of doing things.
> 
> If if were up to me (and I know that it is not), I would disallow 
> linking of weak symbols at module load time altogether.

The semantics were choosen by Rusty who maintains the generic part of the
module loader.  Ensuring the right load order is the job of depmod
and modprobe.

  Ralf

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