[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <02dd2437-32fa-31aa-4ff3-b33a058f2363@huawei.com>
Date: Sat, 25 Mar 2023 14:38:15 +0800
From: Kefeng Wang <wangkefeng.wang@...wei.com>
To: Mike Rapoport <rppt@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>
CC: Arnd Bergmann <arnd@...db.de>,
Catalin Marinas <catalin.marinas@....com>,
Christophe Leroy <christophe.leroy@...roup.eu>,
"David S. Miller" <davem@...emloft.net>,
Dinh Nguyen <dinguyen@...nel.org>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
Guo Ren <guoren@...nel.org>,
John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
Max Filippov <jcmvbkbc@...il.com>,
Michael Ellerman <mpe@...erman.id.au>,
Rich Felker <dalias@...c.org>,
Russell King <linux@...linux.org.uk>,
Will Deacon <will@...nel.org>,
Yoshinori Sato <ysato@...rs.sourceforge.jp>,
Zi Yan <ziy@...dia.com>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-csky@...r.kernel.org>, <linux-ia64@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <linux-m68k@...ts.linux-m68k.org>,
<linux-mm@...ck.org>, <linux-sh@...r.kernel.org>,
<linux-xtensa@...ux-xtensa.org>, <linuxppc-dev@...ts.ozlabs.org>,
<sparclinux@...r.kernel.org>
Subject: Re: [PATCH v3 05/14] ia64: don't allow users to override
ARCH_FORCE_MAX_ORDER
On 2023/3/25 14:08, Mike Rapoport wrote:
> From: "Mike Rapoport (IBM)" <rppt@...nel.org>
>
> It is enough to keep default values for base and huge pages without
> letting users to override ARCH_FORCE_MAX_ORDER.
>
> Drop the prompt to make the option unvisible in *config.
>
> Acked-by: Kirill A. Shutemov <kirill.shutemov@...ux.intel.com>
> Reviewed-by: Zi Yan <ziy@...dia.com>
> Signed-off-by: Mike Rapoport (IBM) <rppt@...nel.org>
> ---
> arch/ia64/Kconfig | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/arch/ia64/Kconfig b/arch/ia64/Kconfig
> index 0d2f41fa56ee..b61437cae162 100644
> --- a/arch/ia64/Kconfig
> +++ b/arch/ia64/Kconfig
> @@ -202,8 +202,7 @@ config IA64_CYCLONE
> If you're unsure, answer N.
>
> config ARCH_FORCE_MAX_ORDER
> - int "MAX_ORDER (10 - 16)" if !HUGETLB_PAGE
> - range 10 16 if !HUGETLB_PAGE
> + int
> default "16" if HUGETLB_PAGE
> default "10"
>
It seems that we could drop the following part?
diff --git a/arch/ia64/include/asm/sparsemem.h
b/arch/ia64/include/asm/sparsemem.h
index a58f8b466d96..18187551b183 100644
--- a/arch/ia64/include/asm/sparsemem.h
+++ b/arch/ia64/include/asm/sparsemem.h
@@ -11,11 +11,6 @@
#define SECTION_SIZE_BITS (30)
#define MAX_PHYSMEM_BITS (50)
-#ifdef CONFIG_ARCH_FORCE_MAX_ORDER
-#if (CONFIG_ARCH_FORCE_MAX_ORDER + PAGE_SHIFT > SECTION_SIZE_BITS)
-#undef SECTION_SIZE_BITS
-#define SECTION_SIZE_BITS (CONFIG_ARCH_FORCE_MAX_ORDER + PAGE_SHIFT)
-#endif
#endif
Powered by blists - more mailing lists