lkml.org 
[lkml]   [2012]   [Mar]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
Patch in this message
/
From
Subject[PATCH 11/11] dynamic_debug: init with core_initcall, not arch_initcall
Date
From: Jim Cromie <jim.cromie@gmail.com>

Initializing dynamic_debug earlier makes pr_debug useful earlier
in boot process. For example:

dyndbg=" module params +p"

will enable parameter processing for initcall levels after core.
Note that this is too late to enable params processing for builtin
modules, which is a significant limitation, but its still
potentially useful.

RFC: This works for me on a 64 bit desktop and i586 SBC, but is
untested on other arches. I presume there is or was a reason
it was done with arch_initcall, maybe the constraints have changed.

Signed-off-by: Jim Cromie <jim.cromie@gmail.com>
---
lib/dynamic_debug.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/lib/dynamic_debug.c b/lib/dynamic_debug.c
index 8fcead5..747245d 100644
--- a/lib/dynamic_debug.c
+++ b/lib/dynamic_debug.c
@@ -1009,7 +1009,7 @@ out_free:
return 0;
}
/* Allow early initialization for boot messages via boot param */
-arch_initcall(dynamic_debug_init);
+core_initcall(dynamic_debug_init);

/* Debugfs setup must be done later */
module_init(dynamic_debug_init_debugfs);
--
1.7.7.6


\
 
 \ /
  Last update: 2012-03-15 00:05    [W:0.340 / U:0.016 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site