diff options
author | Jim Cromie <jim.cromie@gmail.com> | 2012-04-27 14:30:42 -0600 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2012-04-30 16:26:31 -0400 |
commit | 3ec5652ab70f6e9a888d9e5f67c858af354323b3 (patch) | |
tree | 309ed6abea9f994da93a33576aeaf07cefe2562b /lib/syscall.c | |
parent | 29e36c9ffb696ed8d73e1aee713d483ec74a9a43 (diff) | |
download | linux-3.10-3ec5652ab70f6e9a888d9e5f67c858af354323b3.tar.gz linux-3.10-3ec5652ab70f6e9a888d9e5f67c858af354323b3.tar.bz2 linux-3.10-3ec5652ab70f6e9a888d9e5f67c858af354323b3.zip |
dynamic_debug: init with early_initcall, not arch_initcall
1- Call dynamic_debug_init() from early_initcall, not arch_initcall.
2- Call dynamic_debug_init_debugfs() from fs_initcall, not module_init.
RFC: This works for me on a 64 bit desktop and a i586 SBC, but is
untested on other arches. I presume there is or was a reason
original code used arch_initcall, maybe the constraints have changed.
This makes facility available as soon as possible.
2nd change has a downside when dynamic_debug.verbose=1; all the
vpr_info()s called in the proc-fs code are activated, causing
voluminous output from dmesg. TBD: Im unsure of this explanation, but
the output is there. This could be fixed by changing those callsites
to v2pr_info(if verbose > 1).
1st change is still not early enough to enable pr_debugs in
kernel/params, so parsing of boot-args isnt logged. The reparse of
those args is however visible after params.dyndbg="+p" is processed.
Signed-off-by: Jim Cromie <jim.cromie@gmail.com>
Acked-by: Jason Baron <jbaron@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'lib/syscall.c')
0 files changed, 0 insertions, 0 deletions