From: "Jan Beulich" <JBeulich@novell.com>
To: "Rusty Russell" <rusty@rustcorp.com.au>
Cc: <tony.luck@intel.com>,
"Benjamin Herrenschmidt" <benh@kernel.crashing.org>,
"Tim Abbott" <tabbott@mit.edu>, <sam@ravnborg.org>,
"Paul Mackerras" <paulus@samba.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] also discard .*init sections after module initialization
Date: Wed, 01 Jul 2009 08:04:03 +0100 [thread overview]
Message-ID: <4A4B2683020000780000862F@vpn.id2.novell.com> (raw)
In-Reply-To: <200907011452.26720.rusty@rustcorp.com.au>
>>> Rusty Russell <rusty@rustcorp.com.au> 01.07.09 07:22 >>>
>On Tue, 30 Jun 2009 09:27:26 pm Jan Beulich wrote:
>> Just like .init, these sections are supposed to be unneeded after init,
>> and modpost warns about improper section references anyway.
>
>Tim Abbot had a section renaming patch, for -ffunction-sections. Can we kill
>two birds with one stone and have a unique string for init sections, and
>another for exit sections?
Not sure, would need to see what that patch does first. And then, the patch
here doesn't do any renaming.
>> Likewise
>> for .*exit which, other than .exit, aren't needed for the module unload
>> path.
>
>Currently true, but I can't see that being true in general.
Why? .*exit sections deal with device/memory/CPU hot remove, which is
orthogonal to module unload.
Jan
next prev parent reply other threads:[~2009-07-01 7:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 11:57 Jan Beulich
2009-07-01 5:22 ` Rusty Russell
2009-07-01 7:04 ` Jan Beulich [this message]
2009-07-06 15:55 ` Tim Abbott
2009-07-07 6:27 ` Jan Beulich
2009-07-01 7:28 ` Amerigo Wang
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=4A4B2683020000780000862F@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=rusty@rustcorp.com.au \
--cc=sam@ravnborg.org \
--cc=tabbott@mit.edu \
--cc=tony.luck@intel.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
all inboxes | Powered by JetHome®