Re: CONFIG_PRINTK_TIME woes

Andrew Morton
2005-08-21T09:17:43Z

Andrew Morton <akpm@osdl.org> wrote:
>
> How about we give each arch a printk_clock()?

Which might be as simple as this..

--- devel/kernel/printk.c~printk_clock 2005-08-21 02:14:05.000000000 -0700
+++ devel-akpm/kernel/printk.c 2005-08-21 02:15:14.000000000 -0700
@@ -488,6 +488,11 @@ static int __init printk_time_setup(char

__setup("time", printk_time_setup);

+__attribute__((weak)) unsigned long long printk_clock(void)
+{
+ return sched_clock();
+}
+
/*
* This is printk. It can be called from any context. We want it to work.
*
@@ -558,7 +563,7 @@ asmlinkage int vprintk(const char *fmt,
loglev_char = default_message_loglevel
+ '0';
}
- t = sched_clock();
+ t = printk_clock();
nanosec_rem = do_div(t, 1000000000);
tlen = sprintf(tbuf,
"<%c>[%5lu.%06lu] ",
_