public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Xie XiuQi <xiexiuqi@huawei.com>
To: Borislav Petkov <bp@suse.de>
Cc: Ingo Molnar <mingo@redhat.com>, Ingo Molnar <mingo@elte.hu>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Li Bin <huawei.libin@huawei.com>
Subject: Re: [PATCH v2][TRIVIAL] x86/smpboot: fix cpu bootup message
Date: Tue, 24 Dec 2013 09:09:02 +0800	[thread overview]
Message-ID: <52B8DEAE.2040100@huawei.com> (raw)
In-Reply-To: <20131223133402.GA4487@pd.tnic>

On 2013/12/23 21:34, Borislav Petkov wrote:
> On Mon, Dec 23, 2013 at 04:33:00PM +0800, Xie XiuQi wrote:
>> When CPU0 and CPU1 aren't in same package, we got message
>> like this:
>>

[...]

>>
>> diff --git a/arch/x86/kernel/smpboot.c b/arch/x86/kernel/smpboot.c
>> index 85dc05a..9e82c1e 100644
>> --- a/arch/x86/kernel/smpboot.c
>> +++ b/arch/x86/kernel/smpboot.c
>> @@ -639,7 +639,7 @@ static void announce_cpu(int cpu, int apicid)
>>  {
>>  	static int current_node = -1;
>>  	int node = early_cpu_to_node(cpu);
>> -	static int width, node_width;
>> +	static int width, node_width, padding;
>>
>>  	if (!width)
>>  		width = num_digits(num_possible_cpus()) + 1; /* + '#' sign */
>> @@ -658,11 +658,13 @@ static void announce_cpu(int cpu, int apicid)
>>
>>  			printk(KERN_INFO ".... node %*s#%d, CPUs:  ",
>>  			       node_width - num_digits(node), " ", node);
>> -		}
>>
>> -		/* Add padding for the BSP */
>> -		if (cpu == 1)
>> -			pr_cont("%*s", width + 1, " ");
>> +			/* Add padding for the BSP */
>> +			if (!padding && (early_cpu_to_node(0) == current_node)) {
> 
> You don't need "padding".
> 

On another machine, the configuration is:

xiexiuqi@localhost:~> lscpu
[...]
NUMA node0 CPU(s):     4-7,12-15
NUMA node1 CPU(s):     0-3,8-11

Without "padding", we'll get message like this:

[    0.349339] x86: Booting SMP configuration:
[    0.353504] .... node  #1, CPUs:        #1  #2  #3
[    0.398812] .... node  #0, CPUs:    #4  #5  #6  #7
[    0.535186] .... node  #1, CPUs:        #8  #9 #10 #11
[    0.594312] .... node  #0, CPUs:   #12 #13 #14 #15
[    0.652398] x86: Booted up 2 nodes, 16 CPUs


  reply	other threads:[~2013-12-24  1:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-23  8:33 [PATCH v2][TRIVIAL] x86/smpboot: fix cpu bootup message Xie XiuQi
2013-12-23 13:34 ` Borislav Petkov
2013-12-24  1:09   ` Xie XiuQi [this message]
2013-12-24  1:34     ` Yinghai Lu
2013-12-24  3:52       ` Xie XiuQi
2013-12-24  6:09         ` Yinghai Lu
2013-12-24 10:35     ` Borislav Petkov
2013-12-24 18:30       ` Yinghai Lu

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=52B8DEAE.2040100@huawei.com \
    --to=xiexiuqi@huawei.com \
    --cc=bp@suse.de \
    --cc=huawei.libin@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mingo@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox