From: Magnus Damm <magnus.damm@gmail.com>
To: Malcolm Rowe <malcolm-linux@farside.org.uk>
Cc: Magnus Damm <damm@opensource.se>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][RFC] disable built-in modules V2
Date: Wed, 6 Apr 2005 15:10:15 +0200 [thread overview]
Message-ID: <aec7e5c305040606104c86712c@mail.gmail.com> (raw)
In-Reply-To: <courier.4253BAD7.000018D2@mail.farside.org.uk>
On Apr 6, 2005 12:32 PM, Malcolm Rowe <malcolm-linux@farside.org.uk> wrote:
> Magnus Damm writes:
> > Here comes version 2 of the disable built-in patch.
>
> > +void __init disable_initcall(void *fn)
> > +{
> > + initcall_t *call;
> > +
> > + for (call = __initcall_start; call < __initcall_end; call++) {
> > +
> > + if (*call == fn)
> > + *call = NULL;
> > + }
> > +}
>
> Regardless of anything else, won't this break booting with initcall_debug on
> PPC64/IA64 machines? (see the definition of print_fn_descriptor_symbol() in
> kallsyms.h)
Correct, thanks for pointing that out. The code below is probably better:
static void __init do_initcalls(void)
{
initcall_t *call;
@@ -547,6 +558,9 @@ static void __init do_initcalls(void)
for (call = __initcall_start; call < __initcall_end; call++) {
char *msg;
+ if (!*call)
+ continue;
+
if (initcall_debug) {
printk(KERN_DEBUG "Calling initcall 0x%p", *call);
print_fn_descriptor_symbol(": %s()", (unsigned
long) *call);
And I guess the idea of replacing the initcall pointer with NULL will
work both with and without function descriptors, right? So we should
be safe on IA64 and PPC64.
Regards,
/ magnus
next prev parent reply other threads:[~2005-04-06 13:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-05 23:29 [PATCH][RFC] disable built-in modules V2 Magnus Damm
2005-04-06 10:32 ` Malcolm Rowe
2005-04-06 13:10 ` Magnus Damm [this message]
2005-04-06 14:28 ` Malcolm Rowe
2005-04-06 22:14 ` Magnus Damm
2005-04-07 7:47 ` Zwane Mwaikambo
2005-04-07 1:32 ` AsterixTheGaul
2005-04-07 2:23 ` Roland Dreier
2005-04-07 8:23 ` Magnus Damm
2005-04-07 17:01 ` Randy.Dunlap
2005-04-07 17:22 ` Richard B. Johnson
2005-04-07 17:29 ` Randy.Dunlap
2005-04-07 18:53 ` Magnus Damm
2005-04-09 1:42 ` Herbert Xu
2005-04-09 9:43 ` Magnus Damm
2005-04-09 9:48 ` Herbert Xu
2005-04-09 10:03 ` Magnus Damm
2005-04-09 10:07 ` Herbert Xu
2005-04-09 10:14 ` Magnus Damm
2005-04-07 17:37 ` Dave Jones
2005-04-07 2:38 ` Horst von Brand
2005-04-07 21:33 ` Magnus Damm
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=aec7e5c305040606104c86712c@mail.gmail.com \
--to=magnus.damm@gmail.com \
--cc=damm@opensource.se \
--cc=linux-kernel@vger.kernel.org \
--cc=malcolm-linux@farside.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.