From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <51A212E1.40806@gmail.com> Date: Sun, 26 May 2013 21:49:21 +0800 From: Hush Bensen MIME-Version: 1.0 To: KOSAKI Motohiro CC: Michal Hocko , Wanpeng Li , Andrew Morton , KAMEZAWA Hiroyuki , David Rientjes , Jiang Liu , Tang Chen , "linux-mm@kvack.org" , LKML , Greg Kroah-Hartman , stable@vger.kernel.org Subject: Re: [patch v2 3/6] mm/memory_hotplug: Disable memory hotremove for 32bit References: <1369547921-24264-1-git-send-email-liwanp@linux.vnet.ibm.com> <1369547921-24264-3-git-send-email-liwanp@linux.vnet.ibm.com> <20130526090054.GE10651@dhcp22.suse.cz> <51A203D4.6080001@gmail.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: 于 2013/5/26 21:06, KOSAKI Motohiro 写道: > On Sun, May 26, 2013 at 8:45 AM, Hush Bensen wrote: >> 于 2013/5/26 19:58, KOSAKI Motohiro 写道: >> >>>>> As KOSAKI Motohiro mentioned, memory hotplug don't support 32bit since >>>>> it was born, >>>> Why? any reference? This reasoning is really weak. >>> I have no seen any highmem support in memory hotplug code and I don't >>> think this >>> patch fixes all 32bit highmem issue. If anybody are interesting to >>> support it, it is good thing. But in fact, _now_ it is broken when >>> enable HIGHMEM. >> >> But online/offline memory can work well when enable HIGHMEM, isn't it? > If you are lucky. I think it can work well on my x86_32 with highmem enable box.