diff options
author | Dominik Brodowski <linux@dominikbrodowski.net> | 2011-03-27 17:04:46 +0400 |
---|---|---|
committer | Dave Jones <davej@redhat.com> | 2011-05-04 19:50:57 +0400 |
commit | 2d06d8c49afdcc9bb35a85039fa50f0fe35bd40e (patch) | |
tree | d933a68fc71f6e2c3b95b744a87fa1d817bea3d6 /arch/x86/kernel/vsyscall_64.c | |
parent | 27ecddc2a9f99ce4ac9a59a0acd77f7100b6d034 (diff) | |
download | linux-2d06d8c49afdcc9bb35a85039fa50f0fe35bd40e.tar.xz |
[CPUFREQ] use dynamic debug instead of custom infrastructure
With dynamic debug having gained the capability to report debug messages
also during the boot process, it offers a far superior interface for
debug messages than the custom cpufreq infrastructure. As a first step,
remove the old cpufreq_debug_printk() function and replace it with a call
to the generic pr_debug() function.
How can dynamic debug be used on cpufreq? You need a kernel which has
CONFIG_DYNAMIC_DEBUG enabled.
To enabled debugging during runtime, mount debugfs and
$ echo -n 'module cpufreq +p' > /sys/kernel/debug/dynamic_debug/control
for debugging the complete "cpufreq" module. To achieve the same goal during
boot, append
ddebug_query="module cpufreq +p"
as a boot parameter to the kernel of your choice.
For more detailled instructions, please see
Documentation/dynamic-debug-howto.txt
Signed-off-by: Dominik Brodowski <linux@dominikbrodowski.net>
Signed-off-by: Dave Jones <davej@redhat.com>
Diffstat (limited to 'arch/x86/kernel/vsyscall_64.c')
0 files changed, 0 insertions, 0 deletions