From: Dou Liyang <douly.fnst@cn.fujitsu.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: <tglx@linutronix.de>, <hpa@zytor.com>, <bp@alien8.de>,
<wanpeng.li@hotmail.com>, <nicstange@gmail.com>, <x86@kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86/acpi: Fix a warning message in logical CPU IDs allocation
Date: Wed, 1 Mar 2017 18:09:34 +0800 [thread overview]
Message-ID: <0ba0028a-53ea-9c46-e2df-be3e4dadf60b@cn.fujitsu.com> (raw)
In-Reply-To: <20170301091007.GB23669@gmail.com>
Hi Ingo,
At 03/01/2017 05:10 PM, Ingo Molnar wrote:
>
> * Dou Liyang <douly.fnst@cn.fujitsu.com> wrote:
>
>> Current warning message regarded the "nr_cpu_ids - 1" as the limit
>> number of the CPUs. It may be confused us, for example:
>> we have two CPUs, nr_cpu_ids = 2, but the warning message may
>> indicate that we just have 1 CPU, which likes that:
>> Only 1 processors supported.Processor 2/0x2 and the rest
>> are ignored.
>>
>> Fix the warning message, replace "nr_cpu_ids - 1" with "nr_cpu_ids".
>> And the warning message can be like that:
>> APIC: NR_CPUS/possible_cpus limit of 2 reached. Processor 2/0x2
>> and the rest are ignored.
>>
>> Signed-off-by: Dou Liyang <douly.fnst@cn.fujitsu.com>
>
> The patch is correct, but the title is wrong (it's 'apic', not 'acpi'), plus the
> changelog is unreadable. Furthermore the changelog does not declare the changing
> of the return code to -EINVAL ...
>
> I fixed all that in the commit below, but please be more careful in the future.
>
Got it! I see, I will be more careful. :)
Thanks,
Liyang.
> Thanks,
>
> Ingo
>
> =======================>
>>From bb3f0a52630c84807fca9bdd76ac2f5dcec82689 Mon Sep 17 00:00:00 2001
> From: Dou Liyang <douly.fnst@cn.fujitsu.com>
> Date: Tue, 28 Feb 2017 13:50:52 +0800
> Subject: [PATCH] x86/apic: Fix a warning message in logical CPU IDs allocation
>
> The current warning message in allocate_logical_cpuid() is somewhat confusing:
>
> Only 1 processors supported.Processor 2/0x2 and the rest are ignored.
>
> As it might imply that there's only one CPU in the system - while what we ran
> into here is a kernel limitation.
>
> Fix the warning message to clarify all that:
>
> APIC: NR_CPUS/possible_cpus limit of 2 reached. Processor 2/0x2 and the rest are ignored.
>
> ( Also update the error return from -1 to -EINVAL, which is the more
> canonical return value. )
>
> Signed-off-by: Dou Liyang <douly.fnst@cn.fujitsu.com>
> Cc: Linus Torvalds <torvalds@linux-foundation.org>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: bp@alien8.de
> Cc: nicstange@gmail.com
> Cc: wanpeng.li@hotmail.com
> Link: http://lkml.kernel.org/r/1488261052-25753-1-git-send-email-douly.fnst@cn.fujitsu.com
> Signed-off-by: Ingo Molnar <mingo@kernel.org>
> ---
> arch/x86/kernel/apic/apic.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/arch/x86/kernel/apic/apic.c b/arch/x86/kernel/apic/apic.c
> index 4261b3282ad9..11088b86e5c7 100644
> --- a/arch/x86/kernel/apic/apic.c
> +++ b/arch/x86/kernel/apic/apic.c
> @@ -2062,10 +2062,10 @@ static int allocate_logical_cpuid(int apicid)
>
> /* Allocate a new cpuid. */
> if (nr_logical_cpuids >= nr_cpu_ids) {
> - WARN_ONCE(1, "Only %d processors supported."
> + WARN_ONCE(1, "APIC: NR_CPUS/possible_cpus limit of %i reached. "
> "Processor %d/0x%x and the rest are ignored.\n",
> - nr_cpu_ids - 1, nr_logical_cpuids, apicid);
> - return -1;
> + nr_cpu_ids, nr_logical_cpuids, apicid);
> + return -EINVAL;
> }
>
> cpuid_to_apicid[nr_logical_cpuids] = apicid;
>
>
>
next prev parent reply other threads:[~2017-03-01 10:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 5:50 Dou Liyang
2017-03-01 9:10 ` Ingo Molnar
2017-03-01 10:09 ` Dou Liyang [this message]
2017-03-01 9:14 ` [tip:x86/urgent] x86/apic: " tip-bot for Dou Liyang
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=0ba0028a-53ea-9c46-e2df-be3e4dadf60b@cn.fujitsu.com \
--to=douly.fnst@cn.fujitsu.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=nicstange@gmail.com \
--cc=tglx@linutronix.de \
--cc=wanpeng.li@hotmail.com \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome