Re: [PATCH 1/5] x86: Limit the number of processor bootup messages

[Mike Travis]

Yinghai Lu wrote:
> On Tue, Nov 17, 2009 at 4:22 PM, Mike Travis <travis@xxxxxxx> 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 new cpu bootup sequence 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
>
> how about
> Booting Node   0, Processors  #1/0x01 #2/0x02 #3....
> append apic id in hex after the numbering.?
>
> YH

The APIC id's are already listed earlier in the log.  There are
some other APIC patches to deal with making the output clearer
as well as more/less verbose.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/