diff options
| author | Roland Dreier <rdreier@cisco.com> | 2009-09-23 15:33:23 -0700 |
|---|---|---|
| committer | Ingo Molnar <mingo@elte.hu> | 2009-09-24 11:35:19 +0200 |
| commit | ea01c0d7315d6e3218fd22a6947c5b09305fcf65 (patch) | |
| tree | eb89de83cfb03f66447c911b6f5f6e60168bfb5b /arch/x86/kernel/tsc_sync.c | |
| parent | 11868a2dc4f5e4f2f652bfd259e1360193fcee62 (diff) | |
| download | linux-stable-ea01c0d7315d6e3218fd22a6947c5b09305fcf65.tar.gz linux-stable-ea01c0d7315d6e3218fd22a6947c5b09305fcf65.tar.bz2 linux-stable-ea01c0d7315d6e3218fd22a6947c5b09305fcf65.zip | |
x86: Reduce verbosity of "TSC is reliable" message
On modern systems, the kernel prints the message
Skipping synchronization checks as TSC is reliable.
once for every non-boot CPU.
This gets kind of ridiculous on huge systems; for example, on a
64-thread system I was lucky enough to get:
$ dmesg | grep 'TSC is reliable' | wc
63 567 4221
There's no point to doing this for every CPU, since the code is
just checking the boot CPU anyway, so change this to a
printk_once() to make the message appears only once.
Signed-off-by: Roland Dreier <rolandd@cisco.com>
LKML-Reference: <adazl8l2swc.fsf@cisco.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'arch/x86/kernel/tsc_sync.c')
| -rw-r--r-- | arch/x86/kernel/tsc_sync.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/x86/kernel/tsc_sync.c b/arch/x86/kernel/tsc_sync.c index 027b5b498993..f37930954d15 100644 --- a/arch/x86/kernel/tsc_sync.c +++ b/arch/x86/kernel/tsc_sync.c @@ -114,7 +114,7 @@ void __cpuinit check_tsc_sync_source(int cpu) return; if (boot_cpu_has(X86_FEATURE_TSC_RELIABLE)) { - pr_info("Skipping synchronization checks as TSC is reliable.\n"); + printk_once(KERN_INFO "Skipping synchronization checks as TSC is reliable.\n"); return; } |