summaryrefslogtreecommitdiffstats
path: root/drivers/acpi/arm64
diff options
context:
space:
mode:
authorMike Kravetz <mike.kravetz@oracle.com>2021-10-05 22:25:29 +0200
committerCatalin Marinas <catalin.marinas@arm.com>2021-10-11 19:45:19 +0200
commit2e5809a4ddb15969503e43b06662a9a725f613ea (patch)
treef714a1faff3965da0160f347a615a39413861d01 /drivers/acpi/arm64
parentarm64: Restore forced disabling of KPTI on ThunderX (diff)
downloadlinux-2e5809a4ddb15969503e43b06662a9a725f613ea.tar.xz
linux-2e5809a4ddb15969503e43b06662a9a725f613ea.zip
arm64/hugetlb: fix CMA gigantic page order for non-4K PAGE_SIZE
For non-4K PAGE_SIZE configs, the largest gigantic huge page size is CONT_PMD_SHIFT order. On arm64 with 64K PAGE_SIZE, the gigantic page is 16G. Therefore, one should be able to specify 'hugetlb_cma=16G' on the kernel command line so that one gigantic page can be allocated from CMA. However, when adding such an option the following message is produced: hugetlb_cma: cma area should be at least 8796093022208 MiB This is because the calculation for non-4K gigantic page order is incorrect in the arm64 specific routine arm64_hugetlb_cma_reserve(). Fixes: abb7962adc80 ("arm64/hugetlb: Reserve CMA areas for gigantic pages on 16K and 64K configs") Cc: <stable@vger.kernel.org> # 5.9.x Signed-off-by: Mike Kravetz <mike.kravetz@oracle.com> Reviewed-by: Anshuman Khandual <anshuman.khandual@arm.com> Link: https://lore.kernel.org/r/20211005202529.213812-1-mike.kravetz@oracle.com Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
Diffstat (limited to 'drivers/acpi/arm64')
0 files changed, 0 insertions, 0 deletions