From: Andrew Morton <akpm@osdl.org>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Print function names during do_initcall debugging
Date: Tue, 9 Mar 2004 15:09:13 -0800 [thread overview]
Message-ID: <20040309150913.16d4d628.akpm@osdl.org> (raw)
In-Reply-To: <20040309222559.GX17857@lug-owl.de>
Jan-Benedict Glaw <jbglaw@lug-owl.de> wrote:
>
> Please merge the following patch. It prints __init function names while
> all calls are executed at do_initcalls().
Nice, thanks. I tried to do this in the original patch but the kallsyms
stuff wasn't set up at that stage. Someone must have moved something.
However I suspect you didn't test it with CONFIG_KALLSYMS=n: it will be
missing newlines in the output.
25-akpm/init/main.c | 8 ++++++--
1 files changed, 6 insertions(+), 2 deletions(-)
diff -puN init/main.c~initcall_debug-print_symbol init/main.c
--- 25/init/main.c~initcall_debug-print_symbol Tue Mar 9 15:07:16 2004
+++ 25-akpm/init/main.c Tue Mar 9 15:07:59 2004
@@ -37,6 +37,7 @@
#include <linux/profile.h>
#include <linux/rcupdate.h>
#include <linux/moduleparam.h>
+#include <linux/kallsyms.h>
#include <linux/writeback.h>
#include <linux/cpu.h>
#include <linux/efi.h>
@@ -513,8 +514,11 @@ static void __init do_initcalls(void)
for (call = &__initcall_start; call < &__initcall_end; call++) {
char *msg;
- if (initcall_debug)
- printk("calling initcall 0x%p\n", *call);
+ if (initcall_debug) {
+ printk(KERN_DEBUG "Calling initcall 0x%p", *call);
+ print_symbol(": %s()", (unsigned long) *call);
+ printk("\n");
+ }
(*call)();
_
prev parent reply other threads:[~2004-03-09 23:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-09 22:25 Jan-Benedict Glaw
2004-03-09 23:09 ` Andrew Morton [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=20040309150913.16d4d628.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=jbglaw@lug-owl.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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®