The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Takashi Iwai <tiwai@suse.de>, lkml <linux-kernel@vger.kernel.org>,
	akpm <akpm@linux-foundation.org>,
	perex@suse.cz
Subject: Re: [PATCH -mm] ALSA portman2x4 section mismatch
Date: Thu, 28 Jun 2007 20:15:21 +0200	[thread overview]
Message-ID: <20070628181521.GA8011@uranus.ravnborg.org> (raw)
In-Reply-To: <20070628102438.cafa1b41.randy.dunlap@oracle.com>

On Thu, Jun 28, 2007 at 10:24:38AM -0700, Randy Dunlap wrote:
> On Wed, 27 Jun 2007 12:02:32 +0200 Takashi Iwai wrote:
> 
> > At Tue, 26 Jun 2007 15:30:13 -0700,
> > Randy Dunlap wrote:
> > > 
> > > From: Randy Dunlap <randy.dunlap@oracle.com>
> > > 
> > > FIx section mismatch when CONFIG_HOTPLUG=n:
> > > 
> > > WARNING: sound/built-in.o(.exit.text+0x271): Section mismatch: reference to .init.text:snd_p
> > > ortman_unregister_all (between 'snd_portman_module_exit' and 'alsa_mpu401_uart_exit')
> > > 
> > > Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
> > 
> > I applied it to ALSA tree now because it's the simplest way to fix
> > this warning.  But, I'm still wondering whether it was really wrong.
> > 
> > The function snd_portmap_unregister_all() is called both from the
> > module init and exit functions.  Would the module_exit function be
> > called even CONFIG_MODULE=n ?
> 
> No, it's not called when the driver is built-in.
> 
> > If not, __init_or_module should be
> > correct since the function is called only from module_init.
> 
> [adding Sam to cc:]
> 
> I see.  So to try to summarize:
> 
> When CONFIG_MODULES=n, __exit functions can be allowed to reference
> __init functions since the __init functions won't be called because
> the __exit functions are not invoked.
> 
> Does that sound correct?
In the CONFIG_MODULES=n case the __exit section is discarded so yes they
can reference anything without causing breakage.
But that said this is by no means a logical thing to allow from the principle
of minimum suprise.

>  Can & should modpost add this knowledge?
So modpost should not have this knowledge. A better approach is either to fix
the relations or drom the __init/__exit marker for a few sections.
The __init/__exit parts are mainly of benefit in two cases:
1) When someone has a lot of built-in drivers
2) In the embedded world with scarce memory

As for 1) this is a non-typical case not worth optimizing too much against.
As for 2) this is where the biggest benefit are.

Considering this alsa drivers are likely not typical embedded so here dropping a few
__init/__exit markings should be safe.
But it also depends on what other code is invoked from these functions.

	Sam

      reply	other threads:[~2007-06-28 18:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-26 22:30 [PATCH -mm] ALSA portman2x4 section mismatch Randy Dunlap
2007-06-27 10:02 ` Takashi Iwai
2007-06-28 17:24   ` Randy Dunlap
2007-06-28 18:15     ` Sam Ravnborg [this message]

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=20070628181521.GA8011@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@suse.cz \
    --cc=randy.dunlap@oracle.com \
    --cc=tiwai@suse.de \
    /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