acrn-kernel/arch/arm64/kvm/hyp/nvhe
Kirill A. Shutemov 7becae7cdf mm, treewide: redefine MAX_ORDER sanely
MAX_ORDER currently defined as number of orders page allocator supports:
user can ask buddy allocator for page order between 0 and MAX_ORDER-1.

This definition is counter-intuitive and lead to number of bugs all over
the kernel.

Change the definition of MAX_ORDER to be inclusive: the range of orders
user can ask from buddy allocator is 0..MAX_ORDER now.

[kirill@shutemov.name: fix min() warning]
  Link: https://lkml.kernel.org/r/20230315153800.32wib3n5rickolvh@box
[akpm@linux-foundation.org: fix another min_t warning]
[kirill@shutemov.name: fixups per Zi Yan]
  Link: https://lkml.kernel.org/r/20230316232144.b7ic4cif4kjiabws@box.shutemov.name
[akpm@linux-foundation.org: fix underlining in docs]
  Link: https://lore.kernel.org/oe-kbuild-all/202303191025.VRCTk6mP-lkp@intel.com/
Link: https://lkml.kernel.org/r/20230315113133.11326-11-kirill.shutemov@linux.intel.com
Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
Reviewed-by: Michael Ellerman <mpe@ellerman.id.au>	[powerpc]
Cc: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: Zi Yan <ziy@nvidia.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
2023-07-18 13:23:04 +08:00
..
.gitignore
Makefile
cache.S
debug-sr.c
early_alloc.c
gen-hyprel.c
host.S
hyp-init.S
hyp-main.c
hyp-smp.c
hyp.lds.S
list_debug.c
mem_protect.c
mm.c
page_alloc.c mm, treewide: redefine MAX_ORDER sanely 2023-07-18 13:23:04 +08:00
pkvm.c
psci-relay.c
setup.c
stacktrace.c
switch.c
sys_regs.c
sysreg-sr.c
timer-sr.c
tlb.c