From: Bob Picco <bob.picco@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH 1/4] V4 ia64 SPARSEMEM - Kconfig and Makefile
Date: Thu, 22 Sep 2005 17:31:35 +0000 [thread overview]
Message-ID: <20050922173135.GB16066@localhost.localdomain> (raw)
In-Reply-To: <20050922161425.GX16066@localhost.localdomain>
Greg Edwards wrote: [Thu Sep 22 2005, 12:38:59PM EDT]
> On Thu, Sep 22, 2005 at 12:14:25PM -0400, Bob Picco wrote:
> |
> | The patch modifies the Kconfig file to introduce the new memory model
> | options and other related SPARSEMEM changes. There is also a minor change
> | in the Makefile.
>
> This doesn't seem to be working entirely yet. If I make sn2_defconfig
> and manually switch to SPARSEMEM_MANUAL it does the right thing.
>
> If I make the generic defconfig, and switch it to SPARSEMEM_MANUAL,
> VIRTUAL_MEM_MAP is still left on:
>
> [...]
> CONFIG_IA64_GENERIC=y
> [...]
> CONFIG_SELECT_MEMORY_MODEL=y
> # CONFIG_FLATMEM_MANUAL is not set
> # CONFIG_DISCONTIGMEM_MANUAL is not set
> CONFIG_SPARSEMEM_MANUAL=y
> CONFIG_DISCONTIGMEM=y
> CONFIG_SPARSEMEM=y
> CONFIG_NEED_MULTIPLE_NODES=y
> CONFIG_HAVE_MEMORY_PRESENT=y
> # CONFIG_SPARSEMEM_STATIC is not set
> CONFIG_SPARSEMEM_EXTREME=y
> CONFIG_ARCH_SELECT_MEMORY_MODEL=y
> CONFIG_ARCH_FLATMEM_ENABLE=y
> CONFIG_ARCH_DISCONTIGMEM_ENABLE=y
> CONFIG_ARCH_DISCONTIGMEM_DEFAULT=y
> CONFIG_ARCH_SPARSEMEM_ENABLE=y
> CONFIG_NUMA=y
> CONFIG_VIRTUAL_MEM_MAP=y
> CONFIG_HOLES_IN_ZONE=y
> CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID=y
> [...]
Greg,
Thanks for catching this. Just too many memory model permutations. Hopefully
someday just SPARSEMEM and NUMA. I think what is best here is to remove these
Kconfig options from IA64_GENERIC.
- select VIRTUAL_MEM_MAP
- select DISCONTIGMEM
This works for both config files you tested.
bob
prev parent reply other threads:[~2005-09-22 17:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-22 16:14 [PATCH 1/4] V4 ia64 SPARSEMEM - Kconfig and Makefile Bob Picco
2005-09-22 16:38 ` Greg Edwards
2005-09-22 17:31 ` Bob Picco [this message]
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=20050922173135.GB16066@localhost.localdomain \
--to=bob.picco@hp.com \
--cc=linux-ia64@vger.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