summaryrefslogtreecommitdiffstats
path: root/drivers/s390
diff options
context:
space:
mode:
authorDavid Hildenbrand <david@redhat.com>2020-07-01 16:18:30 +0200
committerHeiko Carstens <hca@linux.ibm.com>2020-07-10 15:08:14 +0200
commitfa49066fc326b78e7141d68387179f8968e0e1f0 (patch)
tree1f4a1e404db88797537b55ec1e7cd11a754a22b7 /drivers/s390
parent776499058167d9f41c8eb468e21fe2d241c0b8e6 (diff)
downloadlinux-stable-fa49066fc326b78e7141d68387179f8968e0e1f0.tar.gz
linux-stable-fa49066fc326b78e7141d68387179f8968e0e1f0.tar.bz2
linux-stable-fa49066fc326b78e7141d68387179f8968e0e1f0.zip
s390/mm: don't set ARCH_KEEP_MEMBLOCK
Commit 50be63450728 ("s390/mm: Convert bootmem to memblock") mentions "The original bootmem allocator is getting replaced by memblock. To cover the needs of the s390 kdump implementation the physical memory list is used." As we can now reference "physmem" managed in the memblock allocator after init even without ARCH_KEEP_MEMBLOCK, and s390x does no longer need other memblock metadata after boot (esp., the zcore memmap device that used it got removed), we can stop setting ARCH_KEEP_MEMBLOCK. With this change, we no longer create memblocks for standby/hotplugged memory (added via add_memory()) and free up memblock metadata (except physmem) after boot. Cc: Vasily Gorbik <gor@linux.ibm.com> Cc: Christian Borntraeger <borntraeger@de.ibm.com> Cc: Philipp Rudo <prudo@linux.ibm.com> Cc: Mike Rapoport <rppt@linux.ibm.com> Cc: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: David Hildenbrand <david@redhat.com> Message-Id: <20200701141830.18749-3-david@redhat.com> Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
Diffstat (limited to 'drivers/s390')
0 files changed, 0 insertions, 0 deletions