Re: [tip:x86/boot] x86/boot: Further compress CPUs bootup message

From: Borislav Petkov
Date: Wed Oct 02 2013 - 09:55:37 EST


On Wed, Oct 02, 2013 at 02:20:20PM +0200, Peter Zijlstra wrote:
> > [ 0.314494] smpboot: Booting Node 0, Processors # 1[ 0.333365] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
> > # 2 # 3 # 4 # 5 OK
> > [ 0.398473] smpboot: Booting Node 1, Processors # 6 # 7 # 8 # 9 # 10 # 11 OK
> > [ 0.565198] smpboot: Booting Node 0, Processors # 12 # 13 # 14 # 15 # 16 # 17 OK
> > [ 0.654558] smpboot: Booting Node 1, Processors # 18 # 19 # 20 # 21 # 22 # 23 OK
> > [ 0.743527] Brought up 24 CPUs
>
> operator error here.. this was from the (old) fallback kernel; the new
> one didn't actually boot.

FWIW, this will happen, regardless of what we do:

[ 0.089350] x86: Booting SMP configuration:
[ 0.104355] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
[ 0.089427] .... node #0, CPUs: #1 #2 #3
[ 0.136301] x86: Booted up 1 node, 4 CPUs
[ 0.136442] smpboot: Total of 4 processors activated (23146.32 BogoMIPS)

as the NMI watchdog thing keeps shouting in-between. Do we still need it
- I mean, how can I really use the info that NMI watchdog is consuming a
perf counter? I mean I know how, but do people actually use that info or
everyone knows already? :-)

Thanks.

--
Regards/Gruss,
Boris.

Sent from a fat crate under my desk. Formatting is fine.
--
--
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/