DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type:content-transfer-encoding;
        b=bayaF7CRlh+GF4ihKdiWsDIB90JtddF7nOBQFfcjVgljjBzkMJuAEl63U2/Haz++kN
         FpPY95hkaATqNxL0v2zH9uFT+JFjADC3f+zRDBMBwrxBU1KR87Ot8UUtk4gqUdI9/Ycl
         xmwV51nX/o1pnNoOro9oJ3pRPm2s92KzUw/Qk=
MIME-Version: 1.0
In-Reply-To: <20091117191757.651569000@alcatraz.americas.sgi.com>
References: <20091117191752.164451000@alcatraz.americas.sgi.com>
	 <20091117191757.651569000@alcatraz.americas.sgi.com>
Date: Tue, 17 Nov 2009 12:10:34 -0800
Message-ID: <86802c440911171210x4780c08cg3b3260afd5d2bc5d@mail.gmail.com>
Subject: Re: [PATCH 1/5] x86: Limit the number of processor bootup messages
From: Yinghai Lu <yhlu.kernel@gmail.com>
To: Mike Travis <travis@sgi.com>
Cc: Ingo Molnar <mingo@elte.hu>, 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>, "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
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1434
Lines: 38

On Tue, Nov 17, 2009 at 11:17 AM, Mike Travis <travis@sgi.com> wrote:
> When there are a large number of processors in a system, there
> is an excessive amount of messages sent to the system console.
> It's estimated that with 4096 processors in a system, and the
> console baudrate set to 56K, the startup messages will take
> about 84 minutes to clear the serial port.
>
> This set of patches limits the number of repetitious messages
> which contain no additional information. ?Much of this information
> is obtainable from the /proc and /sysfs. ? Some of the messages
> are also sent to the kernel log buffer as KERN_DEBUG messages so
> dmesg can be used to examine more closely any details specific to
> a problem.
>
> The list of message transformations....
>
> For system_state == SYSTEM_BOOTING:
>
> Booting Node ? 0, Processors ?#1 #2 #3 #4 #5 #6 #7 Ok.
> Booting Node ? 1, Processors ?#8 #9 #10 #11 #12 #13 #14 #15 Ok.
> ..
> Booting Node ? 3, Processors ?#56 #57 #58 #59 #60 #61 #62 #63 Ok.
> Brought up 64 CPUs
>
> The following lines have been removed:
>
> ? ? ? ?CPU: Physical Processor ID:
> ? ? ? ?CPU: Processor Core ID:
> ? ? ? ?CPU %d/0x%x -> Node %d

please don't.

YH
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/