summaryrefslogtreecommitdiffstats
path: root/arch/mips/loongson64/reset.c
diff options
context:
space:
mode:
authorMike Rapoport <rppt@linux.ibm.com>2021-04-18 12:35:12 +0300
committerThomas Bogendoerfer <tsbogend@alpha.franken.de>2021-05-11 22:20:02 +0200
commitcf5b6a94787315c13fdf6736931071eac7f434c6 (patch)
tree8d05030051002d94c2f5acb838b786e8b8b99bac /arch/mips/loongson64/reset.c
parent6efb943b8616ec53a5e444193dccf1af9ad627b5 (diff)
downloadlinux-cf5b6a94787315c13fdf6736931071eac7f434c6.tar.gz
linux-cf5b6a94787315c13fdf6736931071eac7f434c6.tar.bz2
linux-cf5b6a94787315c13fdf6736931071eac7f434c6.zip
MIPS: Octeon: drop dependency on CONFIG_HOLES_IN_ZONE
CAVIUM_OCTEON_SOC configuration selects HOLES_IN_ZONE option to cope with memory crashes that were happening in 2011. This option effectively aliases pfn_valid_within() to pfn_valid() when enabled and hardwires it to 1 when disabled. The check for pfn_valid_within() is only relevant in case the memory map may have holes or undefined struct page instances inside MAX_ORDER chunks. Since 2011 memory management initialization in general and memory map initialization particularly became much more robust so the check for pfn_valid_within() is not required on Octeon even despite its, hmm, unusual memory setup. Remove the selection of HOLES_IN_ZONE by CAVIUM_OCTEON_SOC and drop the HOLES_IN_ZONE configuration option entirely as Octeon was the only MIPS platform to use it. Signed-off-by: Mike Rapoport <rppt@linux.ibm.com> Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Diffstat (limited to 'arch/mips/loongson64/reset.c')
0 files changed, 0 insertions, 0 deletions