From: Borislav Petkov <bp@alien8.de>
To: Ingo Molnar <mingo@kernel.org>
Cc: Yinghai Lu <yinghai@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] x86/boot changes for v3.13
Date: Tue, 12 Nov 2013 12:52:30 +0100 [thread overview]
Message-ID: <20131112115230.GD12849@pd.tnic> (raw)
In-Reply-To: <20131112113710.GA12998@gmail.com>
On Tue, Nov 12, 2013 at 12:37:10PM +0100, Ingo Molnar wrote:
> Hm, I think it's actually a bonus that we see the individual CPUs
> printed as they boot up. That way if there's a hang, the place where
> it hangs is apparent, etc.
Ok, good point.
We can do something like that then:
[ 0.068574] x86: Booting SMP configuration:
[ 0.069006] .... node #1, CPUs: #1
[ 0.147005] .... node #0, CPUs: #2 #3
[ 0.147005] .... node #1, CPUs: #4 #5
[ 0.445273] x86: Booted up 2 nodes, 6 CPUs
and report (node, core) in the order they appear.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2013-11-12 11:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 17:05 [GIT PULL] x86/boot changes for v3.13 Ingo Molnar
2013-11-11 21:37 ` Yinghai Lu
2013-11-12 10:34 ` Borislav Petkov
2013-11-12 11:23 ` Ingo Molnar
2013-11-12 11:32 ` Borislav Petkov
2013-11-12 11:37 ` Ingo Molnar
2013-11-12 11:52 ` Borislav Petkov [this message]
2013-11-12 12:39 ` [PATCH] x86/smpboot: Make the code more consistent Ingo Molnar
2013-11-12 14:04 ` Borislav Petkov
2013-11-12 14:24 ` 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=20131112115230.GD12849@pd.tnic \
--to=bp@alien8.de \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=yinghai@kernel.org \
/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.