[PATCH] x86: Log reason why TSC was marked unstable
commit5a90cf205c922707ffed2d8f87cefd942e96b0ba
authorjohn stultz <johnstul@us.ibm.com>
Wed, 2 May 2007 17:27:08 +0000 (2 19:27 +0200)
committerAndi Kleen <andi@basil.nowhere.org>
Wed, 2 May 2007 17:27:08 +0000 (2 19:27 +0200)
tree5e9c9c1be3d149bff7620db89e1ede2317ba7362
parent2714221985ce6388ec2fa78d7d52e2a5bef78eec
[PATCH] x86: Log reason why TSC was marked unstable

Change mark_tsc_unstable() so it takes a string argument, which holds the
reason the TSC was marked unstable.

This is then displayed the first time mark_tsc_unstable is called.

This should help us better debug why the TSC was marked unstable on certain
systems and allow us to make sure we're not being overly paranoid when
throwing out this troublesome clocksource.

Cc: Ingo Molnar <mingo@elte.hu>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Andi Kleen <ak@suse.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Andi Kleen <ak@suse.de>
arch/i386/kernel/cpu/cyrix.c
arch/i386/kernel/tsc.c
arch/x86_64/kernel/time.c
arch/x86_64/kernel/tsc.c
arch/x86_64/kernel/tsc_sync.c
drivers/acpi/processor_idle.c
include/asm-i386/mach-summit/mach_mpparse.h
include/asm-i386/tsc.h
include/asm-x86_64/timex.h