Re: [PATCH] powerpc/mm: Reinstate ARCH_FORCE_MAX_ORDER ranges

Christophe Leroy writes: > 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

Re: [PATCH] powerpc/mm: Reinstate ARCH_FORCE_MAX_ORDER ranges

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

Re: [PATCH] powerpc/mm: Reinstate ARCH_FORCE_MAX_ORDER ranges

On Fri, 19 May 2023 21:38:06 +1000, Michael Ellerman wrote: > 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 >

[PATCH] powerpc/mm: Reinstate ARCH_FORCE_MAX_ORDER ranges

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