From: Ingo Molnar <mingo@elte.hu>
To: Mike Travis <travis@sgi.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Roland Dreier <rdreier@cisco.com>,
Randy Dunlap <rdunlap@xenotime.net>, Tejun Heo <tj@kernel.org>,
Andi Kleen <andi@firstfloor.org>,
Greg Kroah-Hartman <gregkh@suse.de>,
Yinghai Lu <yhlu.kernel@gmail.com>,
"H. Peter Anvin" <hpa@zytor.com>,
David Rientjes <rientjes@google.com>,
Steven Rostedt <rostedt@goodmis.org>,
Rusty Russell <rusty@rustcorp.com.au>,
Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>,
Jack Steiner <steiner@sgi.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/5] x86: Limit the number of processor bootup messages
Date: Thu, 26 Nov 2009 10:15:59 +0100 [thread overview]
Message-ID: <20091126091559.GG1389@elte.hu> (raw)
In-Reply-To: <20091118002219.163869000@alcatraz.americas.sgi.com>
* Mike Travis <travis@sgi.com> wrote:
> +++ linux/arch/x86/kernel/smpboot.c
> @@ -671,6 +671,27 @@
> complete(&c_idle->done);
> }
>
> +/* reduce the number of lines printed when booting a large cpu count system */
> +static void __cpuinit announce_cpu(int cpu, int apicid)
> +{
> + if (system_state == SYSTEM_BOOTING) {
> +#ifdef CONFIG_NUMA
> + static int current_node = -1;
> + int node = cpu_to_node(cpu);
> +
> + if (node != current_node) {
> + if (current_node > (-1))
> + pr_cont(" Ok.\n");
> + current_node = node;
> + pr_info("Booting Node %3d, Processors ", node);
> + }
> + pr_cont(" #%d%s", cpu, cpu == (nr_cpu_ids - 1) ? " Ok.\n" : "");
> + return;
> +#endif
> + }
That's pretty ugly. (the #ifdef is at the wrong nesting level to begin
with)
Also, cannot we print out the same thing with no #ifdef variances? Users
of UP systems wont be confused by a 'Node 0, CPU 0' message and in 5
years most x86 people will be running NUMA systems.
Ingo
next prev parent reply other threads:[~2009-11-26 9:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 0:22 [PATCH 0/5] Limit console output by suppressing repetitious messages Mike Travis
2009-11-18 0:22 ` [PATCH 1/5] x86: Limit the number of processor bootup messages Mike Travis
2009-11-18 2:45 ` Yinghai Lu
2009-11-18 17:43 ` Mike Travis
2009-11-26 9:15 ` Ingo Molnar [this message]
2009-11-27 21:29 ` [PATCH] " Mike Travis
2009-11-18 0:22 ` [PATCH 2/5] INIT: Limit the number of per cpu calibration " Mike Travis
2009-11-26 9:55 ` [tip:timers/core] timers, init: " tip-bot for Mike Travis
2009-11-18 0:22 ` [PATCH 3/5] firmware: Limit the number of per cpu firmware messages during bootup Mike Travis
2009-11-18 0:22 ` [PATCH 4/5] sched: Limit the number of scheduler debug messages Mike Travis
2009-11-26 9:55 ` [tip:sched/core] " tip-bot for Mike Travis
2009-11-18 0:22 ` [PATCH 5/5] x86: Limit number of per cpu TSC sync messages Mike Travis
2009-11-26 9:55 ` [tip:x86/debug] " tip-bot for Mike Travis
-- strict thread matches above, loose matches on Subject: below --
2009-11-17 19:17 [PATCH 0/5] Limit console output by suppressing repetitious messages Mike Travis
2009-11-17 19:17 ` [PATCH 1/5] x86: Limit the number of processor bootup messages Mike Travis
2009-11-17 20:10 ` Yinghai Lu
2009-11-17 20:29 ` H. Peter Anvin
2009-11-17 21:11 ` Yinghai Lu
2009-11-18 2:38 ` Yinghai Lu
2009-11-18 17:44 ` Mike Travis
2009-11-18 17:43 ` Mike Travis
2009-11-17 21:05 ` Mike Travis
2009-11-18 10:48 ` Borislav Petkov
2009-11-18 17:18 ` Mike Travis
2009-11-18 18:08 ` Borislav Petkov
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=20091126091559.GG1389@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=fweisbec@gmail.com \
--cc=gregkh@suse.de \
--cc=heiko.carstens@de.ibm.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdreier@cisco.com \
--cc=rdunlap@xenotime.net \
--cc=rientjes@google.com \
--cc=rostedt@goodmis.org \
--cc=rusty@rustcorp.com.au \
--cc=seto.hidetoshi@jp.fujitsu.com \
--cc=steiner@sgi.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=travis@sgi.com \
--cc=x86@kernel.org \
--cc=yhlu.kernel@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.