From: "Satyam Sharma" <satyam.sharma@gmail.com>
To: "Jan Beulich" <jbeulich@novell.com>
Cc: "Venkatesh Pallipadi" <venkatesh.pallipadi@intel.com>,
"Sam Ravnborg" <sam@ravnborg.org>, "Andi Kleen" <ak@suse.de>,
linux-kernel@vger.kernel.org, patches@x86-64.org
Subject: Re: [PATCH] x86: fix improper .init-type section references
Date: Tue, 12 Jun 2007 19:39:30 +0530 [thread overview]
Message-ID: <a781481a0706120709v5a2d1147m9d372a8056aeba6d@mail.gmail.com> (raw)
In-Reply-To: <466EC08A.76E4.0078.0@novell.com>
On 6/12/07, Jan Beulich <jbeulich@novell.com> wrote:
> >> And from a purely theoretical
> >> perspective I don't think such references should be considered bad -
> >> .exit.* should be discarded together with .init.* if unloading is
> >> impossible (built-in or configured off), not before module/kernel
> >> initialization.
> >
> >Hmm, but that's not how things are, presently. __exit marked
> >functions are simply not linked into the kernel (when that module
> >is being built-in) at all -- this "discard" happens at _build time_
> >(to save on kernel image size).
>
> Not really, at least not for i386 and x86-64 - see their vmlinux.lds.S files.
For those archs, yes, you're right that modpost should be
special-casing (based on arch) before complaining for
.init -> .exit references.
next prev parent reply other threads:[~2007-06-12 14:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-12 7:48 Jan Beulich
2007-06-12 11:14 ` Satyam Sharma
2007-06-12 12:09 ` Satyam Sharma
2007-06-12 12:43 ` Jan Beulich
2007-06-12 13:32 ` Satyam Sharma
2007-06-12 13:49 ` Jan Beulich
2007-06-12 14:09 ` Satyam Sharma [this message]
2007-06-12 18:00 ` Sam Ravnborg
2007-06-13 3:18 ` Satyam Sharma
2007-06-13 4:35 ` Sam Ravnborg
2007-06-13 6:59 ` Jan Beulich
2007-06-13 7:39 ` Satyam Sharma
2007-06-13 7:49 ` Jan Beulich
2007-06-13 8:10 ` Sam Ravnborg
2007-06-12 17:56 ` Sam Ravnborg
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=a781481a0706120709v5a2d1147m9d372a8056aeba6d@mail.gmail.com \
--to=satyam.sharma@gmail.com \
--cc=ak@suse.de \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@x86-64.org \
--cc=sam@ravnborg.org \
--cc=venkatesh.pallipadi@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®