mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yasunori Goto <y-goto@jp.fujitsu.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Toralf Foerster <toralf.foerster@gmx.de>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Chuck Ebbert <76306.1226@compuserve.com>,
	"Randy.Dunlap" <rdunlap@xenotime.net>,
	Andy Whitcroft <apw@shadowen.org>
Subject: Re: linux-2.6.17.1: undefined reference to `online_page'
Date: Tue, 27 Jun 2006 20:55:24 +0900	[thread overview]
Message-ID: <20060627204448.FBCD.Y-GOTO@jp.fujitsu.com> (raw)
In-Reply-To: <1151343992.10877.34.camel@localhost.localdomain>

> On Mon, 2006-06-26 at 16:39 +0900, Yasunori Goto wrote:
> > 
> > ===================================================================
> > --- linux-2.6.17.orig/mm/Kconfig        2006-06-26 14:19:11.000000000
> > +0900
> > +++ linux-2.6.17/mm/Kconfig     2006-06-26 14:19:53.000000000 +0900
> > @@ -115,7 +115,7 @@ config SPARSEMEM_EXTREME
> >  # eventually, we can have this option just 'select SPARSEMEM'
> >  config MEMORY_HOTPLUG
> >         bool "Allow for memory hot-add"
> > -       depends on SPARSEMEM && HOTPLUG && !SOFTWARE_SUSPEND
> > +       depends on SPARSEMEM && HOTPLUG && !SOFTWARE_SUSPEND
> > && !(X86_32 && !HIGHMEM)
> >  
> >  comment "Memory hotplug is currently incompatible with Software
> > Suspend"
> >         depends on SPARSEMEM && HOTPLUG && SOFTWARE_SUSPEND 
> 
> I think it makes a lot more sense to just disable sparsemem when !
> HIGHMEM.  Plus, we can do all of that in the arch-specific Kconfigs and
> not litter the generic ones with this stuff.

Ah, Ok.
I changed this patch as you said.

At first, I thought it might not be good that config memory hotplug was
disabled by config sparsemem. Because, they are not strictly the same. 
But, this is reasonable way for 2.6.17.x. It is less impact, anyway.

Thanks.

------

Memory hotplug code of i386 adds memory to only highmem.
So, if CONFIG_HIGHMEM is not set, CONFIG_MEMORY_HOTPLUG shouldn't be
set. Otherwise, it causes compile error.

But, CONFIG_MEMORY_HOTPLUG is defined mm/Kconfig. So, if it is disabled
on its file when arch is i386 and highmem is not set, 
it may be a bit intrusive.

When CONFIG_SPARSEMEM is not set, its config option is not set too.
CONFIG_ARCH_SPARSEMEM_ENABLE is defined in arch/i386/Kconfig.
Disabling it is not intrusive for other archtecture.

This is patch for it.


Signed-off-by: Yasunori Goto <y-goto@jp.fujitsu.com>

---
 arch/i386/Kconfig |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Index: linux-2.6.17/arch/i386/Kconfig
===================================================================
--- linux-2.6.17.orig/arch/i386/Kconfig	2006-06-27 19:33:39.000000000 +0900
+++ linux-2.6.17/arch/i386/Kconfig	2006-06-27 19:38:53.000000000 +0900
@@ -562,7 +562,7 @@ config ARCH_DISCONTIGMEM_DEFAULT
 
 config ARCH_SPARSEMEM_ENABLE
 	def_bool y
-	depends on (NUMA || (X86_PC && EXPERIMENTAL))
+	depends on (NUMA || (X86_PC && EXPERIMENTAL)) && HIGHMEM
 	select SPARSEMEM_STATIC
 
 config ARCH_SELECT_MEMORY_MODEL

-- 
Yasunori Goto 



  reply	other threads:[~2006-06-27 11:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-25 21:01 Chuck Ebbert
2006-06-25 21:23 ` Randy.Dunlap
2006-06-26  7:39 ` Yasunori Goto
2006-06-26 17:46   ` Dave Hansen
2006-06-27 11:55     ` Yasunori Goto [this message]
2006-06-27 12:10     ` Andy Whitcroft
2006-06-28  2:27       ` Yasunori Goto
2006-06-29  3:21         ` [PATCH] solve config broken: " Yasunori Goto
2006-06-29 14:58           ` Dave Hansen
2006-06-30  2:14           ` Chris Wright
2006-06-30  2:20             ` Chris Wright
  -- strict thread matches above, loose matches on Subject: below --
2006-06-23  8:01 linux-2.6.17.1: " Toralf Förster

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=20060627204448.FBCD.Y-GOTO@jp.fujitsu.com \
    --to=y-goto@jp.fujitsu.com \
    --cc=76306.1226@compuserve.com \
    --cc=apw@shadowen.org \
    --cc=haveblue@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=toralf.foerster@gmx.de \
    /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

Powered by JetHome