diff options
author | Tony Breeds <tony@bakeyournoodle.com> | 2007-07-04 14:04:31 +1000 |
---|---|---|
committer | Paul Mackerras <paulus@samba.org> | 2007-07-10 22:00:54 +1000 |
commit | fc9069fe56d9594b7a6da0b9f9ca0eafd756260f (patch) | |
tree | 8d069dc5614f30459168bca35608bd2e8edc7790 /drivers | |
parent | 4bb092811c72685f5ba26340d393c0717f5a43b1 (diff) |
[POWERPC] Modify sched_clock() to make CONFIG_PRINTK_TIME more sane
When booting a current kernel with CONFIG_PRINTK_TIME enabled you'll
see messages like:
[ 0.000000] time_init: decrementer frequency = 188.044000 MHz
[ 0.000000] time_init: processor frequency = 1504.352000 MHz
[3712914.436297] Console: colour dummy device 80x25
This cause by the initialisation of tb_to_ns_scale in time_init(), suddenly the
multiplication in sched_clock() now does something :). This patch modifies
sched_clock() to report the offset since the machine booted so the same
printk's now look like:
[ 0.000000] time_init: decrementer frequency = 188.044000 MHz
[ 0.000000] time_init: processor frequency = 1504.352000 MHz
[ 0.000135] Console: colour dummy device 80x25
Effectivly including the uptime in printk()s.
This patch makes tb_to_ns_scale and tb_to_ns_shift static and
read_mostly for good measure.
Signed-off-by: Tony Breeds <tony@bakeyournoodle.com>
Signed-off-by: Paul Mackerras <paulus@samba.org>
Diffstat (limited to 'drivers')
0 files changed, 0 insertions, 0 deletions