From: David Hildenbrand <david@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org, linux-s390@vger.kernel.org,
David Hildenbrand <david@redhat.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Kirill Smelkov <kirr@nexedi.com>,
Michael Holzheu <holzheu@linux.vnet.ibm.com>,
Philipp Rudo <prudo@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>
Subject: [PATCH RFC 0/2] s390/mm: don't set ARCH_KEEP_MEMBLOCK
Date: Fri, 17 Apr 2020 17:01:49 +0200 [thread overview]
Message-ID: <20200417150151.17239-1-david@redhat.com> (raw)
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/20200416104707.20219-1-david@redhat.com
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(-)
--
2.25.1
next reply other threads:[~2020-04-17 15:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 15:01 David Hildenbrand [this message]
2020-04-17 15:01 ` [PATCH RFC 1/2] s390/zcore: traverse resources instead of memblocks David Hildenbrand
2020-06-10 11:45 ` Heiko Carstens
2020-06-19 12:47 ` Philipp Rudo
2020-06-19 12:49 ` David Hildenbrand
2020-04-17 15:01 ` [PATCH RFC 2/2] s390/mm: don't set ARCH_KEEP_MEMBLOCK David Hildenbrand
2020-06-26 16:32 ` Heiko Carstens
2020-06-29 12:44 ` Heiko Carstens
2020-06-29 13:02 ` David Hildenbrand
2020-04-29 14:55 ` [PATCH RFC 0/2] " David Hildenbrand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200417150151.17239-1-david@redhat.com \
--to=david@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=gor@linux.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=holzheu@linux.vnet.ibm.com \
--cc=kirr@nexedi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=prudo@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.