Skip to content

RFC s390/mm: don't set ARCH_KEEP_MEMBLOCK

David Hildenbrand linux-mm linux-s390 lkml 1 version Applied

Status from this message: Applied, thanks!

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 RFC Latest2 patches 7 repliesApplied

Patches in v1 Applied

#Subject and filesSizeRepliesApplied
1/2s390/zcore: traverse resources instead of memblocksdrivers/s390/char/zcore.c+48 -133 replies
2/2s390/mm: don't set ARCH_KEEP_MEMBLOCKarch/s390/Kconfig+0 -13 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH RFC 0/2] s390/mm: don't set ARCH_KEEP_MEMBLOCK

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

After [1] we will no longer create memblocks for hotplugged memory in case of !CONFIG_ARCH_KEEP_MEMBLOCK. With this series, the same will apply to standby memory on s390x, added via add_memory().

[1] https://lkml.kernel.org/r/[email protected]

David Hildenbrand (2):
s390/zcore: traverse resources instead of memblocks s390/mm: don't set ARCH_KEEP_MEMBLOCK

 arch/s390/Kconfig         |  1 -
 drivers/s390/char/zcore.c | 61 ++++++++++++++++++++++++++++++---------
 2 files changed, 48 insertions(+), 14 deletions(-)
Signature · 1 line
2.25.1

Read the cover letter in its thread