From: Huacai Chen <chenhuacai@kernel.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: WANG Xuerui <kernel@xen0n.name>,
loongarch@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] loongarch: select ARCH_ENABLE_THP_MIGRATION instead of redefining it
Date: Tue, 6 Feb 2024 12:04:16 +0800 [thread overview]
Message-ID: <CAAhV-H6Wfu4-X0zUJgwEpFC9DNCP5BPFQ0Dazo_fWXLpxzqK6w@mail.gmail.com> (raw)
In-Reply-To: <20240204134813.61884-1-masahiroy@kernel.org>
Queued, thanks.
Huacai
On Sun, Feb 4, 2024 at 9:48 PM Masahiro Yamada <masahiroy@kernel.org> wrote:
>
> ARCH_ENABLE_THP_MIGRATION is supposed to be selected by arch Kconfig.
>
> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
> ---
>
> arch/loongarch/Kconfig | 5 +----
> 1 file changed, 1 insertion(+), 4 deletions(-)
>
> diff --git a/arch/loongarch/Kconfig b/arch/loongarch/Kconfig
> index 10959e6c3583..64e9a01c7f36 100644
> --- a/arch/loongarch/Kconfig
> +++ b/arch/loongarch/Kconfig
> @@ -12,6 +12,7 @@ config LOONGARCH
> select ARCH_DISABLE_KASAN_INLINE
> select ARCH_ENABLE_MEMORY_HOTPLUG
> select ARCH_ENABLE_MEMORY_HOTREMOVE
> + select ARCH_ENABLE_THP_MIGRATION if TRANSPARENT_HUGEPAGE
> select ARCH_HAS_ACPI_TABLE_UPGRADE if ACPI
> select ARCH_HAS_CPU_FINALIZE_INIT
> select ARCH_HAS_FORTIFY_SOURCE
> @@ -667,10 +668,6 @@ config ARCH_SPARSEMEM_ENABLE
> or have huge holes in the physical address space for other reasons.
> See <file:Documentation/mm/numa.rst> for more.
>
> -config ARCH_ENABLE_THP_MIGRATION
> - def_bool y
> - depends on TRANSPARENT_HUGEPAGE
> -
> config ARCH_MEMORY_PROBE
> def_bool y
> depends on MEMORY_HOTPLUG
> --
> 2.40.1
>
>
prev parent reply other threads:[~2024-02-06 4:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-04 13:48 [PATCH] loongarch: select ARCH_ENABLE_THP_MIGRATION instead of redefining it Masahiro Yamada
2024-02-06 4:04 ` Huacai Chen [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=CAAhV-H6Wfu4-X0zUJgwEpFC9DNCP5BPFQ0Dazo_fWXLpxzqK6w@mail.gmail.com \
--to=chenhuacai@kernel.org \
--cc=kernel@xen0n.name \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=masahiroy@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).