From: "Zheng, Shaohui" <shaohui.zheng@intel.com>
To: David Rientjes <rientjes@google.com>, Tejun Heo <tj@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"haicheng.li@linux.intel.com" <haicheng.li@linux.intel.com>,
"lethal@linux-sh.org" <lethal@linux-sh.org>,
Andi Kleen <ak@linux.intel.com>,
"dave@linux.vnet.ibm.com" <dave@linux.vnet.ibm.com>,
Greg Kroah-Hartman <gregkh@suse.de>, Ingo Molnar <mingo@elte.hu>,
"Brown, Len" <len.brown@intel.com>,
Yinghai Lu <Yinghai.Lu@sun.com>,
"Li, Haicheng" <haicheng.li@intel.com>,
Shaohui Zheng <shaohui.zheng@linux.intel.com>
Subject: RE: [5/7,v8] NUMA Hotplug Emulator: Support cpu probe/release in x86_64
Date: Fri, 10 Dec 2010 09:35:08 +0800 [thread overview]
Message-ID: <A24AE1FFE7AEC5489F83450EE98351BF2A40FED661@shsmsx502.ccr.corp.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1012081334160.15658@chino.kir.corp.google.com>
Both Tejun's and my patches are under review process, the hotplug emulator patchset is much earlier than Tejun's patch. Currently, I did not know how to handle this situation.
It seems that I have 3 options:
1) continue to send this patchset based on current upstream kernel
2) continue to send this patchset based on upstream kernel + Tejun's patch
3) Postpone the patchset until Tejun's patches are accepted.
Can someone provide some suggestions? Thanks so much.
Thanks & Regards,
Shaohui
-----Original Message-----
From: David Rientjes [mailto:rientjes@google.com]
Sent: Thursday, December 09, 2010 5:37 AM
To: Zheng, Shaohui; Tejun Heo
Cc: Andrew Morton; linux-mm@kvack.org; linux-kernel@vger.kernel.org; haicheng.li@linux.intel.com; lethal@linux-sh.org; Andi Kleen; dave@linux.vnet.ibm.com; Greg Kroah-Hartman; Ingo Molnar; Brown, Len; Yinghai Lu; Li, Haicheng
Subject: Re: [5/7,v8] NUMA Hotplug Emulator: Support cpu probe/release in x86_64
On Tue, 7 Dec 2010, shaohui.zheng@intel.com wrote:
> From: Shaohui Zheng <shaohui.zheng@intel.com>
>
This patch is undoubtedly going to conflict with Tejun's unification of
the 32 and 64 bit NUMA boot paths, specifically the patch at
http://marc.info/?l=linux-kernel&m=129087151912379.
Tejun, what's the status of that patchset posted on November 27? Any
comments about this change?
--
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/ .
Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-12-10 1:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 1:00 [0/7,v8] NUMA Hotplug Emulator (v8) shaohui.zheng
2010-12-07 1:00 ` [1/7,v8] NUMA Hotplug Emulator: documentation shaohui.zheng
2010-12-07 18:24 ` Eric B Munson
2010-12-07 23:20 ` Shaohui Zheng
2010-12-08 17:46 ` Eric B Munson
2010-12-09 0:09 ` Shaohui Zheng
2010-12-08 18:16 ` Eric B Munson
2010-12-08 21:16 ` David Rientjes
2010-12-09 0:23 ` Shaohui Zheng
2010-12-08 21:18 ` David Rientjes
2010-12-09 0:33 ` Shaohui Zheng
2010-12-07 1:00 ` [2/7,v8] NUMA Hotplug Emulator: Add numa=possible option shaohui.zheng
2010-12-07 1:00 ` [3/7,v8] NUMA Hotplug Emulator: Add node hotplug emulation shaohui.zheng
2010-12-07 1:00 ` [4/7,v8] NUMA Hotplug Emulator: Abstract cpu register functions shaohui.zheng
2010-12-07 1:00 ` [5/7,v8] NUMA Hotplug Emulator: Support cpu probe/release in x86_64 shaohui.zheng
2010-12-08 21:36 ` David Rientjes
2010-12-09 9:37 ` Tejun Heo
2010-12-10 8:01 ` Zheng, Shaohui
2010-12-10 1:35 ` Zheng, Shaohui [this message]
2010-12-07 1:00 ` [6/7,v8] NUMA Hotplug Emulator: Fake CPU socket with logical CPU on x86 shaohui.zheng
2010-12-07 1:00 ` [7/7,v8] NUMA Hotplug Emulator: Implement per-node add_memory debugfs interface shaohui.zheng
2010-12-08 21:31 ` David Rientjes
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=A24AE1FFE7AEC5489F83450EE98351BF2A40FED661@shsmsx502.ccr.corp.intel.com \
--to=shaohui.zheng@intel.com \
--cc=Yinghai.Lu@sun.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=dave@linux.vnet.ibm.com \
--cc=gregkh@suse.de \
--cc=haicheng.li@intel.com \
--cc=haicheng.li@linux.intel.com \
--cc=len.brown@intel.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=rientjes@google.com \
--cc=shaohui.zheng@linux.intel.com \
--cc=tj@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