diff options
| author | Mike Kravetz <mike.kravetz@oracle.com> | 2021-10-05 23:25:29 +0300 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2021-10-20 12:44:58 +0300 |
| commit | a31c33aa80a550b3848024533bda215a0aa52e0b (patch) | |
| tree | 8fadcac258a3d1fdb8de13b95dea06bfaa600c62 /drivers/gpu/drm/msm/msm_drv.h | |
| parent | 0c97008859cad117568b3b5cc073993025b59a57 (diff) | |
| download | linux-a31c33aa80a550b3848024533bda215a0aa52e0b.tar.xz | |
arm64/hugetlb: fix CMA gigantic page order for non-4K PAGE_SIZE
commit 2e5809a4ddb15969503e43b06662a9a725f613ea upstream.
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>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/gpu/drm/msm/msm_drv.h')
0 files changed, 0 insertions, 0 deletions