Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758835Ab1EBWUX (ORCPT ); Mon, 2 May 2011 18:20:23 -0400 Received: from router-fw.net-space.pl ([89.174.63.77]:46772 "EHLO router-fw.net-space.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756982Ab1EBWUU (ORCPT ); Mon, 2 May 2011 18:20:20 -0400 Date: Tue, 3 May 2011 00:18:57 +0200 From: Daniel Kiper To: Dave Hansen Cc: Daniel Kiper , ian.campbell@citrix.com, akpm@linux-foundation.org, andi.kleen@intel.com, haicheng.li@linux.intel.com, fengguang.wu@intel.com, jeremy@goop.org, konrad.wilk@oracle.com, dan.magenheimer@oracle.com, v.tolstov@selfip.ru, pasik@iki.fi, wdauchy@gmail.com, rientjes@google.com, xen-devel@lists.xensource.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org Subject: Re: [PATCH 1/4] mm: Remove dependency on CONFIG_FLATMEM from online_page() Message-ID: <20110502221857.GJ4623@router-fw-old.local.net-space.pl> References: <20110502211915.GB4623@router-fw-old.local.net-space.pl> <1304371504.30823.45.camel@nimitz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1304371504.30823.45.camel@nimitz> User-Agent: Mutt/1.3.28i Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1636 Lines: 34 On Mon, May 02, 2011 at 02:25:04PM -0700, Dave Hansen wrote: > On Mon, 2011-05-02 at 23:19 +0200, Daniel Kiper wrote: > > Memory hotplug code strictly depends on CONFIG_SPARSEMEM. > > It means that code depending on CONFIG_FLATMEM in online_page() > > is never compiled. Remove it because it is not needed anymore. > > It's subtle, but I don't think that's true. We had another hotplug mode > for x86_64 before folks were comfortable turning SPARSEMEM on for the > whole architecture. It was quite possible to have memory hotplug > without sparsemem in that case. I think Keith Mannthey did some of that > code if I remember right. > > But, I'm not sure how much of that stayed in distros versus made it > upstream. In any case, you might want to chase down the > X86_64_ACPI_NUMA bit to make sure it can't be used with FLATMEM ever. > > config MEMORY_HOTPLUG > bool "Allow for memory hot-add" > depends on SPARSEMEM || X86_64_ACPI_NUMA > depends on HOTPLUG && ARCH_ENABLE_MEMORY_HOTPLUG > depends on (IA64 || X86 || PPC_BOOK3S_64 || SUPERH || S390) IIRC some time ago it was possible to enable memory hotplug with CONFIG_FLATMEM. That is why I looked for any dependencies of memory hoplug code on CONFIG_FLATMEM in current Linux Kernel source. I could not find anything and that is why I published this patch. However, maybe I missed something. Daniel -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/