From: Jiang Liu <jiang.liu@linux.intel.com>
To: "Tang Chen" <tangchen@cn.fujitsu.com>,
"Mika Penttilä" <mika.j.penttila@gmail.com>
Cc: rjw@rjwysocki.net, gongzhaogang@inspur.com, x86@kernel.org,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH 3/5] x86, acpi, cpu-hotplug: Introduce apicid_to_cpuid[] array to store persistent cpuid <-> apicid mapping.
Date: Wed, 15 Jul 2015 13:35:05 +0800 [thread overview]
Message-ID: <55A5F109.3020705@linux.intel.com> (raw)
In-Reply-To: <55A5D4A5.8040806@cn.fujitsu.com>
On 2015/7/15 11:33, Tang Chen wrote:
> Hi Mika,
>
> On 07/07/2015 07:14 PM, Mika Penttilä wrote:
>> I think you forgot to reserve CPU 0 for BSP in cpuid mask.
>
> Sorry for the late reply.
>
> I'm not familiar with BSP. Do you mean in get_cpuid(),
> I should reserve 0 for physical cpu0 in BSP ?
>
> Would you please share more detail ?
BSP stands for "Bootstrapping Processor". In other word,
BSP is CPU0.
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Jiang Liu <jiang.liu@linux.intel.com>
To: "Tang Chen" <tangchen@cn.fujitsu.com>,
"Mika Penttilä" <mika.j.penttila@gmail.com>
Cc: rjw@rjwysocki.net, gongzhaogang@inspur.com, x86@kernel.org,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH 3/5] x86, acpi, cpu-hotplug: Introduce apicid_to_cpuid[] array to store persistent cpuid <-> apicid mapping.
Date: Wed, 15 Jul 2015 13:35:05 +0800 [thread overview]
Message-ID: <55A5F109.3020705@linux.intel.com> (raw)
In-Reply-To: <55A5D4A5.8040806@cn.fujitsu.com>
On 2015/7/15 11:33, Tang Chen wrote:
> Hi Mika,
>
> On 07/07/2015 07:14 PM, Mika PenttilA? wrote:
>> I think you forgot to reserve CPU 0 for BSP in cpuid mask.
>
> Sorry for the late reply.
>
> I'm not familiar with BSP. Do you mean in get_cpuid(),
> I should reserve 0 for physical cpu0 in BSP ?
>
> Would you please share more detail ?
BSP stands for "Bootstrapping Processor". In other word,
BSP is CPU0.
--
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: Jiang Liu <jiang.liu@linux.intel.com>
To: "Tang Chen" <tangchen@cn.fujitsu.com>,
"Mika Penttilä" <mika.j.penttila@gmail.com>
Cc: rjw@rjwysocki.net, gongzhaogang@inspur.com, x86@kernel.org,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH 3/5] x86, acpi, cpu-hotplug: Introduce apicid_to_cpuid[] array to store persistent cpuid <-> apicid mapping.
Date: Wed, 15 Jul 2015 13:35:05 +0800 [thread overview]
Message-ID: <55A5F109.3020705@linux.intel.com> (raw)
In-Reply-To: <55A5D4A5.8040806@cn.fujitsu.com>
On 2015/7/15 11:33, Tang Chen wrote:
> Hi Mika,
>
> On 07/07/2015 07:14 PM, Mika Penttilä wrote:
>> I think you forgot to reserve CPU 0 for BSP in cpuid mask.
>
> Sorry for the late reply.
>
> I'm not familiar with BSP. Do you mean in get_cpuid(),
> I should reserve 0 for physical cpu0 in BSP ?
>
> Would you please share more detail ?
BSP stands for "Bootstrapping Processor". In other word,
BSP is CPU0.
next prev parent reply other threads:[~2015-07-15 5:35 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 9:30 [PATCH 0/5] Make cpuid <-> nodeid mapping persistent Tang Chen
2015-07-07 9:30 ` Tang Chen
2015-07-07 9:30 ` Tang Chen
2015-07-07 9:30 ` [PATCH 1/5] x86, gfp: Cache best near node for memory allocation Tang Chen
2015-07-07 9:30 ` Tang Chen
2015-07-15 21:48 ` Tejun Heo
2015-07-15 21:48 ` Tejun Heo
2015-08-04 3:36 ` Tang Chen
2015-08-04 3:36 ` Tang Chen
2015-08-04 3:36 ` Tang Chen
2015-08-04 8:05 ` Jiang Liu
2015-08-04 8:05 ` Jiang Liu
2015-08-04 8:24 ` Tang Chen
2015-08-04 8:24 ` Tang Chen
2015-08-04 8:24 ` Tang Chen
2015-08-09 6:15 ` Tang Chen
2015-08-09 6:15 ` Tang Chen
2015-08-12 1:53 ` Jiang Liu
2015-08-12 1:53 ` Jiang Liu
2015-08-04 8:26 ` gongzhaogang
2015-08-04 8:26 ` gongzhaogang
2015-08-04 8:53 ` Tang Chen
2015-08-04 8:58 ` Tang Chen
2015-07-07 9:30 ` [PATCH 2/5] x86, acpi, cpu-hotplug: Enable acpi to register all possible cpus at boot time Tang Chen
2015-07-07 9:30 ` Tang Chen
2015-07-07 9:30 ` [PATCH 3/5] x86, acpi, cpu-hotplug: Introduce apicid_to_cpuid[] array to store persistent cpuid <-> apicid mapping Tang Chen
2015-07-07 9:30 ` Tang Chen
2015-07-07 11:14 ` Mika Penttilä
2015-07-07 11:14 ` Mika Penttilä
2015-07-15 3:33 ` Tang Chen
2015-07-15 3:33 ` Tang Chen
2015-07-15 3:33 ` Tang Chen
2015-07-15 5:35 ` Jiang Liu [this message]
2015-07-15 5:35 ` Jiang Liu
2015-07-15 5:35 ` Jiang Liu
2015-07-15 6:26 ` Tang Chen
2015-07-15 6:26 ` Tang Chen
2015-07-15 6:26 ` Tang Chen
2015-07-15 22:02 ` Tejun Heo
2015-07-15 22:02 ` Tejun Heo
2015-07-07 9:30 ` [PATCH 4/5] x86, acpi, cpu-hotplug: Enable MADT APIs to return disabled apicid Tang Chen
2015-07-07 9:30 ` Tang Chen
2015-07-15 22:06 ` Tejun Heo
2015-07-15 22:06 ` Tejun Heo
2015-07-07 9:30 ` [PATCH 5/5] x86, acpi, cpu-hotplug: Set persistent cpuid <-> nodeid mapping when booting Tang Chen
2015-07-07 9:30 ` Tang Chen
2015-07-15 22:13 ` [PATCH 0/5] Make cpuid <-> nodeid mapping persistent Tejun Heo
2015-07-15 22:13 ` Tejun Heo
2015-07-23 4:44 ` Tang Chen
2015-07-23 4:44 ` Tang Chen
2015-07-23 4:44 ` Tang Chen
2015-07-23 18:32 ` Tejun Heo
2015-07-23 18:32 ` Tejun Heo
-- strict thread matches above, loose matches on Subject: below --
2015-07-01 4:45 Tang Chen
2015-07-01 4:45 ` [PATCH 3/5] x86, acpi, cpu-hotplug: Introduce apicid_to_cpuid[] array to store persistent cpuid <-> apicid mapping Tang Chen
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=55A5F109.3020705@linux.intel.com \
--to=jiang.liu@linux.intel.com \
--cc=gongzhaogang@inspur.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=rjw@rjwysocki.net \
--cc=tangchen@cn.fujitsu.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 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.