From: Sedat Dilek <sedat.dilek@googlemail.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-mm@kvack.org
Subject: Re: mm/Kconfig: warning: (COMPACTION && EXPERIMENTAL && HUGETLB_PAGE && MMU) selects MIGRATION which has unmet direct dependencies (NUMA || ARCH_ENABLE_MEMORY_HOTREMOVE)
Date: Thu, 9 Sep 2010 18:05:20 +0200 [thread overview]
Message-ID: <AANLkTi=iVDfmCSmHSW2ArZ4MO0k+zDQU9WMy7TvSwhBe@mail.gmail.com> (raw)
In-Reply-To: <20100909082331.7278e76b.randy.dunlap@oracle.com>
Hey Randy!
thanks for the quick response... wanted to start a new build :-).
- Sedat -
On Thu, Sep 9, 2010 at 5:23 PM, Randy Dunlap <randy.dunlap@oracle.com> wrote:
> On Thu, 9 Sep 2010 17:10:34 +0200 Sedat Dilek wrote:
>
>> Hi,
>>
>> while build latest 2.6.36-rc3 I get this warning:
>>
>> [ build.log]
>> ...
>> warning: (COMPACTION && EXPERIMENTAL && HUGETLB_PAGE && MMU) selects
>> MIGRATION which has unmet direct dependencies (NUMA ||
>> ARCH_ENABLE_MEMORY_HOTREMOVE)
>> ...
>>
>> Here the excerpt of...
>>
>> [ mm/Kconfig ]
>> ...
>> # support for memory compaction
>> config COMPACTION
>> bool "Allow for memory compaction"
>> select MIGRATION
>> depends on EXPERIMENTAL && HUGETLB_PAGE && MMU
>> help
>> Allows the compaction of memory for the allocation of huge pages.
>> ...
>>
>> I have set the following kernel-config parameters:
>>
>> $ egrep 'COMPACTION|HUGETLB_PAGE|MMU|MIGRATION|NUMA|ARCH_ENABLE_MEMORY_HOTREMOVE'
>> linux-2.6.36-rc3/debian/build/build_i386_none_686/.config
>> CONFIG_MMU=y
>> # CONFIG_IOMMU_HELPER is not set
>> CONFIG_IOMMU_API=y
>> CONFIG_COMPACTION=y
>> CONFIG_MIGRATION=y
>> CONFIG_MMU_NOTIFIER=y
>> CONFIG_HUGETLB_PAGE=y
>> # CONFIG_IOMMU_STRESS is not set
>>
>> Looks like I have no NUMA or ARCH_ENABLE_MEMORY_HOTREMOVE set.
>>
>> Ok, it is a *warning*...
>
>
> Andrea Arcangeli posted a patch for this on linux-mm on 2010-SEP-03.
> (below)
>
> ---
> From: Andrea Arcangeli <aarcange@redhat.com>
>
> COMPACTION enables MIGRATION, but MIGRATION spawns a warning if numa
> or memhotplug aren't selected. However MIGRATION doesn't depend on
> them. I guess it's just trying to be strict doing a double check on
> who's enabling it, but it doesn't know that compaction also enables
> MIGRATION.
>
> Signed-off-by: Andrea Arcangeli <aarcange@redhat.com>
> ---
>
> diff --git a/mm/Kconfig b/mm/Kconfig
> --- a/mm/Kconfig
> +++ b/mm/Kconfig
> @@ -189,7 +189,7 @@ config COMPACTION
> config MIGRATION
> bool "Page migration"
> def_bool y
> - depends on NUMA || ARCH_ENABLE_MEMORY_HOTREMOVE
> + depends on NUMA || ARCH_ENABLE_MEMORY_HOTREMOVE || COMPACTION
> help
> Allows the migration of the physical location of pages of processes
> while the virtual addresses are not changed. This is useful in
>
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-09-09 16:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-09 15:10 Sedat Dilek
2010-09-09 15:15 ` Sedat Dilek
2010-09-09 15:23 ` Randy Dunlap
2010-09-09 16:05 ` Sedat Dilek [this message]
2010-09-09 16:16 ` Sedat Dilek
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='AANLkTi=iVDfmCSmHSW2ArZ4MO0k+zDQU9WMy7TvSwhBe@mail.gmail.com' \
--to=sedat.dilek@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=randy.dunlap@oracle.com \
--cc=sedat.dilek@gmail.com \
/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