From: Tang Chen <tangchen@cn.fujitsu.com>
To: Tejun Heo <tj@kernel.org>
Cc: jiang.liu@linux.intel.com, mika.j.penttila@gmail.com,
mingo@redhat.com, akpm@linux-foundation.org, rjw@rjwysocki.net,
hpa@zytor.com, yasu.isimatu@gmail.com,
isimatu.yasuaki@jp.fujitsu.com, kamezawa.hiroyu@jp.fujitsu.com,
izumi.taku@jp.fujitsu.com, gongzhaogang@inspur.com,
qiaonuohan@cn.fujitsu.com, x86@kernel.org,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, tangchen@cn.fujitsu.com
Subject: Re: [PATCH v2 5/7] x86, acpi, cpu-hotplug: Introduce apicid_to_cpuid[] array to store persistent cpuid <-> apicid mapping.
Date: Sat, 26 Sep 2015 17:52:09 +0800 [thread overview]
Message-ID: <56066AC9.6020703@cn.fujitsu.com> (raw)
In-Reply-To: <20150910195532.GK8114@mtj.duckdns.org>
Hi tj,
On 09/11/2015 03:55 AM, Tejun Heo wrote:
> Hello,
>
> So, overall, I think this is the right way to go although I have no
> idea whether the acpi part is okay.
Thank you very much for reviewing. :)
>
>> +/*
>> + * Current allocated max logical CPU ID plus 1.
>> + * All allocated CPU ID should be in [0, max_logical_cpuid),
>> + * so the maximum of max_logical_cpuid is nr_cpu_ids.
>> + *
>> + * NOTE: Reserve 0 for BSP.
>> + */
>> +static int max_logical_cpuid = 1;
> Rename it to nr_logical_cpuids and just mention that it's allocated
> contiguously?
OK.
>
>> +static int cpuid_to_apicid[] = {
>> + [0 ... NR_CPUS - 1] = -1,
>> +};
> And maybe mention how the two variables are synchronized?
User should call allocate_logical_cpuid() to get a new logical cpuid.
This allocator will ensure the synchronization.
Will mention it in the comment.
>
>> +static int allocate_logical_cpuid(int apicid)
>> +{
>> + int i;
>> +
>> + /*
>> + * cpuid <-> apicid mapping is persistent, so when a cpu is up,
>> + * check if the kernel has allocated a cpuid for it.
>> + */
>> + for (i = 0; i < max_logical_cpuid; i++) {
>> + if (cpuid_to_apicid[i] == apicid)
>> + return i;
>> + }
>> +
>> + /* Allocate a new cpuid. */
>> + if (max_logical_cpuid >= nr_cpu_ids) {
>> + WARN_ONCE(1, "Only %d processors supported."
>> + "Processor %d/0x%x and the rest are ignored.\n",
>> + nr_cpu_ids - 1, max_logical_cpuid, apicid);
>> + return -1;
>> + }
> So, the original code didn't have this failure mode, why is this
> different for the new code?
It is not different. Since max_logical_cpuid is new, this is ensure it
won't
go beyond NR_CPUS.
Thanks.
>
> Thanks.
>
WARNING: multiple messages have this Message-ID (diff)
From: Tang Chen <tangchen@cn.fujitsu.com>
To: Tejun Heo <tj@kernel.org>
Cc: jiang.liu@linux.intel.com, mika.j.penttila@gmail.com,
mingo@redhat.com, akpm@linux-foundation.org, rjw@rjwysocki.net,
hpa@zytor.com, yasu.isimatu@gmail.com,
isimatu.yasuaki@jp.fujitsu.com, kamezawa.hiroyu@jp.fujitsu.com,
izumi.taku@jp.fujitsu.com, gongzhaogang@inspur.com,
qiaonuohan@cn.fujitsu.com, x86@kernel.org,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, tangchen@cn.fujitsu.com
Subject: Re: [PATCH v2 5/7] x86, acpi, cpu-hotplug: Introduce apicid_to_cpuid[] array to store persistent cpuid <-> apicid mapping.
Date: Sat, 26 Sep 2015 17:52:09 +0800 [thread overview]
Message-ID: <56066AC9.6020703@cn.fujitsu.com> (raw)
In-Reply-To: <20150910195532.GK8114@mtj.duckdns.org>
Hi tj,
On 09/11/2015 03:55 AM, Tejun Heo wrote:
> Hello,
>
> So, overall, I think this is the right way to go although I have no
> idea whether the acpi part is okay.
Thank you very much for reviewing. :)
>
>> +/*
>> + * Current allocated max logical CPU ID plus 1.
>> + * All allocated CPU ID should be in [0, max_logical_cpuid),
>> + * so the maximum of max_logical_cpuid is nr_cpu_ids.
>> + *
>> + * NOTE: Reserve 0 for BSP.
>> + */
>> +static int max_logical_cpuid = 1;
> Rename it to nr_logical_cpuids and just mention that it's allocated
> contiguously?
OK.
>
>> +static int cpuid_to_apicid[] = {
>> + [0 ... NR_CPUS - 1] = -1,
>> +};
> And maybe mention how the two variables are synchronized?
User should call allocate_logical_cpuid() to get a new logical cpuid.
This allocator will ensure the synchronization.
Will mention it in the comment.
>
>> +static int allocate_logical_cpuid(int apicid)
>> +{
>> + int i;
>> +
>> + /*
>> + * cpuid <-> apicid mapping is persistent, so when a cpu is up,
>> + * check if the kernel has allocated a cpuid for it.
>> + */
>> + for (i = 0; i < max_logical_cpuid; i++) {
>> + if (cpuid_to_apicid[i] == apicid)
>> + return i;
>> + }
>> +
>> + /* Allocate a new cpuid. */
>> + if (max_logical_cpuid >= nr_cpu_ids) {
>> + WARN_ONCE(1, "Only %d processors supported."
>> + "Processor %d/0x%x and the rest are ignored.\n",
>> + nr_cpu_ids - 1, max_logical_cpuid, apicid);
>> + return -1;
>> + }
> So, the original code didn't have this failure mode, why is this
> different for the new code?
It is not different. Since max_logical_cpuid is new, this is ensure it
won't
go beyond NR_CPUS.
Thanks.
>
> Thanks.
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Tang Chen <tangchen@cn.fujitsu.com>
To: Tejun Heo <tj@kernel.org>
Cc: <jiang.liu@linux.intel.com>, <mika.j.penttila@gmail.com>,
<mingo@redhat.com>, <akpm@linux-foundation.org>,
<rjw@rjwysocki.net>, <hpa@zytor.com>, <yasu.isimatu@gmail.com>,
<isimatu.yasuaki@jp.fujitsu.com>,
<kamezawa.hiroyu@jp.fujitsu.com>, <izumi.taku@jp.fujitsu.com>,
<gongzhaogang@inspur.com>, <qiaonuohan@cn.fujitsu.com>,
<x86@kernel.org>, <linux-acpi@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
<tangchen@cn.fujitsu.com>
Subject: Re: [PATCH v2 5/7] x86, acpi, cpu-hotplug: Introduce apicid_to_cpuid[] array to store persistent cpuid <-> apicid mapping.
Date: Sat, 26 Sep 2015 17:52:09 +0800 [thread overview]
Message-ID: <56066AC9.6020703@cn.fujitsu.com> (raw)
In-Reply-To: <20150910195532.GK8114@mtj.duckdns.org>
Hi tj,
On 09/11/2015 03:55 AM, Tejun Heo wrote:
> Hello,
>
> So, overall, I think this is the right way to go although I have no
> idea whether the acpi part is okay.
Thank you very much for reviewing. :)
>
>> +/*
>> + * Current allocated max logical CPU ID plus 1.
>> + * All allocated CPU ID should be in [0, max_logical_cpuid),
>> + * so the maximum of max_logical_cpuid is nr_cpu_ids.
>> + *
>> + * NOTE: Reserve 0 for BSP.
>> + */
>> +static int max_logical_cpuid = 1;
> Rename it to nr_logical_cpuids and just mention that it's allocated
> contiguously?
OK.
>
>> +static int cpuid_to_apicid[] = {
>> + [0 ... NR_CPUS - 1] = -1,
>> +};
> And maybe mention how the two variables are synchronized?
User should call allocate_logical_cpuid() to get a new logical cpuid.
This allocator will ensure the synchronization.
Will mention it in the comment.
>
>> +static int allocate_logical_cpuid(int apicid)
>> +{
>> + int i;
>> +
>> + /*
>> + * cpuid <-> apicid mapping is persistent, so when a cpu is up,
>> + * check if the kernel has allocated a cpuid for it.
>> + */
>> + for (i = 0; i < max_logical_cpuid; i++) {
>> + if (cpuid_to_apicid[i] == apicid)
>> + return i;
>> + }
>> +
>> + /* Allocate a new cpuid. */
>> + if (max_logical_cpuid >= nr_cpu_ids) {
>> + WARN_ONCE(1, "Only %d processors supported."
>> + "Processor %d/0x%x and the rest are ignored.\n",
>> + nr_cpu_ids - 1, max_logical_cpuid, apicid);
>> + return -1;
>> + }
> So, the original code didn't have this failure mode, why is this
> different for the new code?
It is not different. Since max_logical_cpuid is new, this is ensure it
won't
go beyond NR_CPUS.
Thanks.
>
> Thanks.
>
next prev parent reply other threads:[~2015-09-26 9:52 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-10 4:27 [PATCH v2 0/7] Make cpuid <-> nodeid mapping persistent Tang Chen
2015-09-10 4:27 ` Tang Chen
2015-09-10 4:27 ` [PATCH v2 1/7] x86, numa: Move definition of find_near_online_node() forward Tang Chen
2015-09-10 4:27 ` Tang Chen
2015-09-10 4:27 ` [PATCH v2 2/7] x86, numa: Introduce a node to node array to map a node to its best online node Tang Chen
2015-09-10 4:27 ` Tang Chen
2015-09-10 4:27 ` [PATCH v2 3/7] x86, gfp: Cache best near node for memory allocation Tang Chen
2015-09-10 4:27 ` Tang Chen
2015-09-10 19:29 ` Tejun Heo
2015-09-10 19:29 ` Tejun Heo
2015-09-10 19:38 ` Tejun Heo
2015-09-10 19:38 ` Tejun Heo
2015-09-10 22:02 ` Christoph Lameter
2015-09-10 22:02 ` Christoph Lameter
2015-09-10 22:08 ` Tejun Heo
2015-09-10 22:08 ` Tejun Heo
2015-09-11 0:14 ` Christoph Lameter
2015-09-11 0:14 ` Christoph Lameter
2015-09-26 9:35 ` Tang Chen
2015-09-26 9:35 ` Tang Chen
2015-09-26 9:35 ` Tang Chen
2015-09-26 9:31 ` Tang Chen
2015-09-26 9:31 ` Tang Chen
2015-09-26 17:53 ` Tejun Heo
2015-09-26 17:53 ` Tejun Heo
2015-09-28 1:50 ` Tang Chen
2015-09-28 1:50 ` Tang Chen
2015-09-10 4:27 ` [PATCH v2 4/7] x86, acpi, cpu-hotplug: Enable acpi to register all possible cpus at boot time Tang Chen
2015-09-10 4:27 ` Tang Chen
2015-09-10 23:10 ` Rafael J. Wysocki
2015-09-10 23:10 ` Rafael J. Wysocki
2015-09-26 9:44 ` Tang Chen
2015-09-26 9:44 ` Tang Chen
2015-09-26 9:44 ` Tang Chen
2015-09-10 4:27 ` [PATCH v2 5/7] x86, acpi, cpu-hotplug: Introduce apicid_to_cpuid[] array to store persistent cpuid <-> apicid mapping Tang Chen
2015-09-10 4:27 ` Tang Chen
2015-09-10 4:27 ` Tang Chen
2015-09-10 19:55 ` Tejun Heo
2015-09-10 19:55 ` Tejun Heo
2015-09-26 9:52 ` Tang Chen [this message]
2015-09-26 9:52 ` Tang Chen
2015-09-26 9:52 ` Tang Chen
2015-09-26 17:56 ` Tejun Heo
2015-09-26 17:56 ` Tejun Heo
2015-09-28 1:57 ` Tang Chen
2015-09-28 1:57 ` Tang Chen
2015-09-10 4:27 ` [PATCH v2 6/7] x86, acpi, cpu-hotplug: Enable MADT APIs to return disabled apicid Tang Chen
2015-09-10 4:27 ` Tang Chen
2015-09-10 4:27 ` Tang Chen
2015-09-10 4:27 ` [PATCH v2 7/7] x86, acpi, cpu-hotplug: Set persistent cpuid <-> nodeid mapping when booting Tang Chen
2015-09-10 4:27 ` Tang Chen
2015-10-23 19:49 ` [PATCH v2 0/7] Make cpuid <-> nodeid mapping persistent Yasuaki Ishimatsu
2015-10-23 19:49 ` Yasuaki Ishimatsu
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=56066AC9.6020703@cn.fujitsu.com \
--to=tangchen@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=gongzhaogang@inspur.com \
--cc=hpa@zytor.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=izumi.taku@jp.fujitsu.com \
--cc=jiang.liu@linux.intel.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mika.j.penttila@gmail.com \
--cc=mingo@redhat.com \
--cc=qiaonuohan@cn.fujitsu.com \
--cc=rjw@rjwysocki.net \
--cc=tj@kernel.org \
--cc=x86@kernel.org \
--cc=yasu.isimatu@gmail.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 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.