|author||Kay Sievers <email@example.com>||2012-05-10 04:30:45 +0200|
|committer||Greg Kroah-Hartman <firstname.lastname@example.org>||2012-05-09 20:35:06 -0700|
printk() - restore timestamp printing at console output
The output of the timestamps got lost with the conversion of the kmsg buffer to records; restore the old behavior. Document, that CONFIG_PRINTK_TIME now only controls the output of the timestamps in the syslog() system call and on the console, and not the recording of the timestamps. Cc: Joe Perches <email@example.com> Cc: Linus Torvalds <firstname.lastname@example.org> Cc: Sasha Levin <email@example.com> Cc: Ingo Molnar <firstname.lastname@example.org> Reported-by: Yinghai Lu <email@example.com> Signed-off-by: Kay Sievers <firstname.lastname@example.org> Signed-off-by: Greg Kroah-Hartman <email@example.com>
Diffstat (limited to 'lib')
1 files changed, 10 insertions, 6 deletions
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index ef8192bc0c3..e1193417703 100644
@@ -3,12 +3,16 @@ config PRINTK_TIME
bool "Show timing information on printks"
depends on PRINTK
- Selecting this option causes timing information to be
- included in printk output. This allows you to measure
- the interval between kernel operations, including bootup
- operations. This is useful for identifying long delays
- in kernel startup. Or add printk.time=1 at boot-time.
- See Documentation/kernel-parameters.txt
+ Selecting this option causes time stamps of the printk()
+ messages to be added to the output of the syslog() system
+ call and at the console.
+ The timestamp is always recorded internally, and exported
+ to /dev/kmsg. This flag just specifies if the timestamp should
+ be included, not that the timestamp is recorded.
+ The behavior is also controlled by the kernel command line
+ parameter printk.time=1. See Documentation/kernel-parameters.txt
int "Default message log level (1-7)"