From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Michael Ellerman <mpe@ellerman.id.au>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Cc: "rppt@kernel.org" <rppt@kernel.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH] powerpc/mm: Reinstate ARCH_FORCE_MAX_ORDER ranges
Date: Fri, 4 Aug 2023 17:32:28 +0000 [thread overview]
Message-ID: <8011d806-5b30-bf26-2bfe-a08c39d57e20@csgroup.eu> (raw)
In-Reply-To: <20230519113806.370635-1-mpe@ellerman.id.au>
Le 19/05/2023 à 13:38, Michael Ellerman a écrit :
> Commit 1e8fed873e74 ("powerpc: drop ranges for definition of
> ARCH_FORCE_MAX_ORDER") removed the limits on the possible values for
> ARCH_FORCE_MAX_ORDER.
>
> However removing the ranges entirely causes some common work flows to
> break. For example building a defconfig (which uses 64K pages), changing
> the page size to 4K, and rebuilding used to work, because
> ARCH_FORCE_MAX_ORDER would be clamped to 12 by the ranges.
>
> With the ranges removed it creates a kernel that builds but crashes at
> boot:
> kernel BUG at mm/huge_memory.c:470!
> Oops: Exception in kernel mode, sig: 5 [#1]
> ...
> NIP hugepage_init+0x9c/0x278
> LR do_one_initcall+0x80/0x320
> Call Trace:
> do_one_initcall+0x80/0x320
> kernel_init_freeable+0x304/0x3ac
> kernel_init+0x30/0x1a0
> ret_from_kernel_user_thread+0x14/0x1c
>
> The reasoning for removing the ranges was that some of the values were
> too large. So take that into account and limit the maximums to 10 which
> is the default max, except for the 4K case which uses 12.
There is something wrong:
~# echo 1 > /sys/kernel/mm/hugepages/hugepages-8192kB/nr_hugepages
sh: write error: Invalid argument
$ grep -e MAX_ORDER -e K_PAGES .config
CONFIG_PPC_4K_PAGES=y
# CONFIG_PPC_16K_PAGES is not set
CONFIG_ARCH_FORCE_MAX_ORDER=10
In the past MAX_ORDER used to be 12 but now it is force to 10.
Christophe
>
> Fixes: 1e8fed873e74 ("powerpc: drop ranges for definition of ARCH_FORCE_MAX_ORDER")
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
> ---
> arch/powerpc/Kconfig | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> I plan to merge this via the powerpc fixes branch.
>
> diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig
> index 539d1f03ff42..bff5820b7cda 100644
> --- a/arch/powerpc/Kconfig
> +++ b/arch/powerpc/Kconfig
> @@ -906,11 +906,17 @@ config DATA_SHIFT
>
> config ARCH_FORCE_MAX_ORDER
> int "Order of maximal physically contiguous allocations"
> + range 7 8 if PPC64 && PPC_64K_PAGES
> default "8" if PPC64 && PPC_64K_PAGES
> + range 12 12 if PPC64 && !PPC_64K_PAGES
> default "12" if PPC64 && !PPC_64K_PAGES
> + range 8 10 if PPC32 && PPC_16K_PAGES
> default "8" if PPC32 && PPC_16K_PAGES
> + range 6 10 if PPC32 && PPC_64K_PAGES
> default "6" if PPC32 && PPC_64K_PAGES
> + range 4 10 if PPC32 && PPC_256K_PAGES
> default "4" if PPC32 && PPC_256K_PAGES
> + range 10 10
> default "10"
> help
> The kernel page allocator limits the size of maximal physically
next prev parent reply other threads:[~2023-08-04 17:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 11:38 Michael Ellerman
2023-07-03 5:21 ` Michael Ellerman
2023-08-04 17:32 ` Christophe Leroy [this message]
2023-08-05 12:41 ` Michael Ellerman
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=8011d806-5b30-bf26-2bfe-a08c39d57e20@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=rppt@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