From: Tang Chen <tangchen@cn.fujitsu.com>
To: Tejun Heo <tj@kernel.org>
Cc: cl@linux.com, 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, x86@kernel.org,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, Gu Zheng <guz.fnst@cn.fujitsu.com>
Subject: Re: [PATCH 5/5] x86, acpi, cpu-hotplug: Set persistent cpuid <-> nodeid mapping when booting.
Date: Wed, 13 Jan 2016 12:56:38 +0800 [thread overview]
Message-ID: <5695D906.2030405@cn.fujitsu.com> (raw)
In-Reply-To: <20160108191305.GA1898@mtj.duckdns.org>
On 01/09/2016 03:13 AM, Tejun Heo wrote:
> Hello, Tang.
>
> On Thu, Jan 07, 2016 at 12:20:25PM +0800, Tang Chen wrote:
>> From: Gu Zheng <guz.fnst@cn.fujitsu.com>
>>
>> This patch finishes step 4.
> This doesn't help people trying to read the patch. If you wanna say
> it's one of the steps of something, you also need to say what the
> steps are. No need to duplicate the whole thing but a short summary
> would be helpful.
Sure. Thx.
>
>> This patch set the persistent cpuid <-> nodeid mapping for all enabled/disabled
>> processors at boot time via an additional acpi namespace walk for processors.
> So, the patchset generally looks good to me although I'm not too
> familiar with acpi. Rafael, Len, what do you think?
>
> 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: <cl@linux.com>, <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>, <x86@kernel.org>,
<linux-acpi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-mm@kvack.org>, Gu Zheng <guz.fnst@cn.fujitsu.com>
Subject: Re: [PATCH 5/5] x86, acpi, cpu-hotplug: Set persistent cpuid <-> nodeid mapping when booting.
Date: Wed, 13 Jan 2016 12:56:38 +0800 [thread overview]
Message-ID: <5695D906.2030405@cn.fujitsu.com> (raw)
In-Reply-To: <20160108191305.GA1898@mtj.duckdns.org>
On 01/09/2016 03:13 AM, Tejun Heo wrote:
> Hello, Tang.
>
> On Thu, Jan 07, 2016 at 12:20:25PM +0800, Tang Chen wrote:
>> From: Gu Zheng <guz.fnst@cn.fujitsu.com>
>>
>> This patch finishes step 4.
> This doesn't help people trying to read the patch. If you wanna say
> it's one of the steps of something, you also need to say what the
> steps are. No need to duplicate the whole thing but a short summary
> would be helpful.
Sure. Thx.
>
>> This patch set the persistent cpuid <-> nodeid mapping for all enabled/disabled
>> processors at boot time via an additional acpi namespace walk for processors.
> So, the patchset generally looks good to me although I'm not too
> familiar with acpi. Rafael, Len, what do you think?
>
> Thanks.
>
next prev parent reply other threads:[~2016-01-13 4:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 4:20 [PATCH v4 0/5] Make cpuid <-> nodeid mapping persistent Tang Chen
2016-01-07 4:20 ` Tang Chen
2016-01-07 4:20 ` [PATCH 1/5] x86, memhp, numa: Online memory-less nodes at boot time Tang Chen
2016-01-07 4:20 ` Tang Chen
2016-01-08 18:28 ` Tejun Heo
2016-01-08 18:28 ` Tejun Heo
2016-01-13 4:56 ` Tang Chen
2016-01-13 4:56 ` Tang Chen
2016-01-07 4:20 ` [PATCH 2/5] x86, acpi, cpu-hotplug: Enable acpi to register all possible cpus " Tang Chen
2016-01-07 4:20 ` Tang Chen
2016-01-07 4:20 ` [PATCH 3/5] x86, acpi, cpu-hotplug: Introduce cpuid_to_apicid[] array to store persistent cpuid <-> apicid mapping Tang Chen
2016-01-07 4:20 ` Tang Chen
2016-01-07 4:20 ` [PATCH 4/5] x86, acpi, cpu-hotplug: Enable MADT APIs to return disabled apicid Tang Chen
2016-01-07 4:20 ` Tang Chen
2016-01-07 4:20 ` [PATCH 5/5] x86, acpi, cpu-hotplug: Set persistent cpuid <-> nodeid mapping when booting Tang Chen
2016-01-07 4:20 ` Tang Chen
2016-01-08 19:13 ` Tejun Heo
2016-01-08 19:13 ` Tejun Heo
2016-01-13 4:56 ` Tang Chen [this message]
2016-01-13 4:56 ` Tang Chen
-- strict thread matches above, loose matches on Subject: below --
2015-07-07 9:30 [PATCH 0/5] Make cpuid <-> nodeid mapping persistent Tang Chen
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-01 4:45 [PATCH 0/5] Make cpuid <-> nodeid mapping persistent Tang Chen
2015-07-01 4:45 ` [PATCH 5/5] x86, acpi, cpu-hotplug: Set persistent cpuid <-> nodeid mapping when booting 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=5695D906.2030405@cn.fujitsu.com \
--to=tangchen@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=gongzhaogang@inspur.com \
--cc=guz.fnst@cn.fujitsu.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=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.