From: tip-bot for Dave Jones <davej@redhat.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
davej@redhat.com, tglx@linutronix.de, mingo@elte.hu
Subject: [tip:x86/debug] x86: Minimise printk spew from per-vendor init code
Date: Sat, 14 Nov 2009 00:33:35 GMT [thread overview]
Message-ID: <tip-0388423dba2217b4e5b6c61690b0506d13b25a49@git.kernel.org> (raw)
In-Reply-To: <20091113203000.GA19160@redhat.com>
Commit-ID: 0388423dba2217b4e5b6c61690b0506d13b25a49
Gitweb: http://git.kernel.org/tip/0388423dba2217b4e5b6c61690b0506d13b25a49
Author: Dave Jones <davej@redhat.com>
AuthorDate: Fri, 13 Nov 2009 15:30:00 -0500
Committer: Ingo Molnar <mingo@elte.hu>
CommitDate: Sat, 14 Nov 2009 01:18:05 +0100
x86: Minimise printk spew from per-vendor init code
In the default case where the kernel supports all CPU vendors,
we currently print out a bunch of not useful messages on every
system.
32-bit:
KERNEL supported cpus:
Intel GenuineIntel
AMD AuthenticAMD
NSC Geode by NSC
Cyrix CyrixInstead
Centaur CentaurHauls
Transmeta GenuineTMx86
Transmeta TransmetaCPU
UMC UMC UMC UMC
64-bit:
KERNEL supported cpus:
Intel GenuineIntel
AMD AuthenticAMD
Centaur CentaurHauls
Given that "what CPUs does the kernel support" isn't useful for
the "support everything" case, we can suppress these printk's.
Signed-off-by: Dave Jones <davej@redhat.com>
LKML-Reference: <20091113203000.GA19160@redhat.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
arch/x86/kernel/cpu/common.c | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/arch/x86/kernel/cpu/common.c b/arch/x86/kernel/cpu/common.c
index cc25c2b..617a29f 100644
--- a/arch/x86/kernel/cpu/common.c
+++ b/arch/x86/kernel/cpu/common.c
@@ -656,6 +656,7 @@ static void __init early_identify_cpu(struct cpuinfo_x86 *c)
void __init early_cpu_init(void)
{
+#ifdef PROCESSOR_SELECT
const struct cpu_dev *const *cdev;
int count = 0;
@@ -676,7 +677,7 @@ void __init early_cpu_init(void)
cpudev->c_ident[j]);
}
}
-
+#endif
early_identify_cpu(&boot_cpu_data);
}
next prev parent reply other threads:[~2009-11-14 0:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-13 20:30 [X86] " Dave Jones
2009-11-14 0:33 ` tip-bot for Dave Jones [this message]
2009-11-14 1:03 ` [tip:x86/debug] x86: " Yinghai Lu
2009-11-14 1:38 ` Dave Jones
2009-11-14 2:48 ` Yinghai Lu
2009-11-14 9:38 ` Ingo Molnar
2009-11-14 10:19 ` [tip:x86/debug] x86: Fix cpu_devs[] initialization in early_cpu_init() tip-bot for Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=tip-0388423dba2217b4e5b6c61690b0506d13b25a49@git.kernel.org \
--to=davej@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome