[lkml]   [2020]   [Jun]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subject[PATCH v1 0/2] s390/mm: don't set ARCH_KEEP_MEMBLOCK
This is the follow-up of [1]:
[PATCH RFC 0/2] s390/mm: don't set ARCH_KEEP_MEMBLOCK

This series is based on the latest s390/features branch, which contains
"s390/zcore: remove memmap device". [2]

Looking into why we still create memblocks for stdnaby/hotplugged memory
(via add_memory()), I discovered that we might not need ARCH_KEEP_MEMBLOCK
on s390x after all.

This is relevant in the context of virtio-mem, where we hotplug a lot of
small memory blocks (and want to avoid managing unused metadata). But also
for existing setups, it might help to free up some memory after boot.

Compile-tested on s390x, pseries, arm64, i386, mips64, powernv, sh, and


RFC -> v1:
- "s390/zcore: traverse resources instead of memblocks" has been replaced
on s390/features by "s390/zcore: remove memmap devic"
- Add "mm/memblock: expose only miminal interface to add/walk physmem"
-- Sort out section mismatch errors when using physmem after boot without
- "s390/mm: don't set ARCH_KEEP_MEMBLOCK"
-- Rephrase description

David Hildenbrand (2):
mm/memblock: expose only miminal interface to add/walk physmem
s390/mm: don't set ARCH_KEEP_MEMBLOCK

arch/s390/Kconfig | 1 -
arch/s390/kernel/crash_dump.c | 6 ++--
include/linux/memblock.h | 17 +++++++---
mm/memblock.c | 63 +++++++++++++++++++----------------
4 files changed, 50 insertions(+), 37 deletions(-)


 \ /
  Last update: 2020-06-30 10:19    [W:0.077 / U:4.228 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site