Commit 8c907785 authored by Mike Rapoport (IBM)'s avatar Mike Rapoport (IBM) Committed by Andrew Morton

arm: reword ARCH_FORCE_MAX_ORDER prompt and help text

Patch series "arch,mm: cleanup Kconfig entries for ARCH_FORCE_MAX_ORDER",
v3.

Several architectures have ARCH_FORCE_MAX_ORDER in their Kconfig and
they all have wrong and misleading prompt and help text for this option.

Besides, some define insane limits for possible values of
ARCH_FORCE_MAX_ORDER, some carefully define ranges only for a subset of
possible configurations, some make this option configurable by users for no
good reason.

This set updates the prompt and help text everywhere and does its best to
update actual definitions of ranges where applicable.

kbuild generated a bunch of false positives because it assigns -1 to
ARCH_FORCE_MAX_ORDER, hopefully this will be fixed soon.


This patch (of 14):

The prompt and help text of ARCH_FORCE_MAX_ORDER are not even close to
describe this configuration option.

Update both to actually describe what this option does.

Link: https://lkml.kernel.org/r/20230325060828.2662773-1-rppt@kernel.org
Link: https://lkml.kernel.org/r/20230324052233.2654090-1-rppt@kernel.org
Link: https://lkml.kernel.org/r/20230324052233.2654090-2-rppt@kernel.orgSigned-off-by: default avatarMike Rapoport (IBM) <rppt@kernel.org>
Acked-by: default avatarKirill A. Shutemov <kirill.shutemov@linux.intel.com>
Reviewed-by: default avatarZi Yan <ziy@nvidia.com>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Catalin Marinas <catalin.marinas@arm.com>
Cc: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: David Miller <davem@davemloft.net>
Cc: Dinh Nguyen <dinguyen@kernel.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Guo Ren <guoren@kernel.org>
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Max Filippov <jcmvbkbc@gmail.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>
Cc: Rich Felker <dalias@libc.org>
Cc: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: Will Deacon <will@kernel.org>
Cc: Yoshinori Sato <ysato@users.sourceforge.jp>
Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
parent 6a792697
...@@ -1354,17 +1354,19 @@ config ARM_MODULE_PLTS ...@@ -1354,17 +1354,19 @@ config ARM_MODULE_PLTS
configurations. If unsure, say y. configurations. If unsure, say y.
config ARCH_FORCE_MAX_ORDER config ARCH_FORCE_MAX_ORDER
int "Maximum zone order" int "Order of maximal physically contiguous allocations"
default "11" if SOC_AM33XX default "11" if SOC_AM33XX
default "8" if SA1111 default "8" if SA1111
default "10" default "10"
help help
The kernel memory allocator divides physically contiguous memory The kernel page allocator limits the size of maximal physically
blocks into "zones", where each zone is a power of two number of contiguous allocations. The limit is called MAX_ORDER and it
pages. This option selects the largest power of two that the kernel defines the maximal power of two of number of pages that can be
keeps in the memory allocator. If you need to allocate very large allocated as a single contiguous block. This option allows
blocks of physically contiguous memory, then you may need to overriding the default setting when ability to allocate very
increase this value. large blocks of physically contiguous memory is required.
Don't change if unsure.
config ALIGNMENT_TRAP config ALIGNMENT_TRAP
def_bool CPU_CP15_MMU def_bool CPU_CP15_MMU
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment