powerpc/fadump: Do not use hugepages when fadump is active
authorHari Bathini <hbathini@linux.vnet.ibm.com>
Tue, 10 Apr 2018 13:41:31 +0000 (19:11 +0530)
committerMichael Ellerman <mpe@ellerman.id.au>
Thu, 3 May 2018 13:09:25 +0000 (23:09 +1000)
commit8597538712ebd90bc83dfb0b3b40398a0c53ad5b
tree4181bb1f936224650a0c38e501cbbfdb56f23050
parentb71a693d3db3abd1ddf7d29be967a1180c3ebb22
powerpc/fadump: Do not use hugepages when fadump is active

FADump capture kernel boots in restricted memory environment preserving
the context of previous kernel to save vmcore. Supporting hugepages in
such environment makes things unnecessarily complicated, as hugepages
need memory set aside for them. This means most of the capture kernel's
memory is used in supporting hugepages. In most cases, this results in
out-of-memory issues while booting FADump capture kernel. But hugepages
are not of much use in capture kernel whose only job is to save vmcore.
So, disabling hugepages support, when fadump is active, is a reliable
solution for the out of memory issues. Introducing a flag variable to
disable HugeTLB support when fadump is active.

Signed-off-by: Hari Bathini <hbathini@linux.vnet.ibm.com>
Reviewed-by: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
arch/powerpc/include/asm/page.h
arch/powerpc/kernel/fadump.c
arch/powerpc/mm/hash_utils_64.c
arch/powerpc/mm/hugetlbpage.c