From: Andrea Reale <ar@linux.vnet.ibm.com>
To: linux-arm-kernel@lists.infradead.org
Cc: m.bielski@virtualopensystems.com, ar@linux.vnet.ibm.com,
scott.branden@broadcom.com, will.deacon@arm.com,
qiuxishi@huawei.com, f.fainelli@gmail.com,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/5] Memory hotplug support for arm64 - complete patchset
Date: Tue, 11 Apr 2017 15:54:10 +0100 [thread overview]
Message-ID: <cover.1491920513.git.ar@linux.vnet.ibm.com> (raw)
Hi all,
this is a follow up to the patch we previously released here [1].
We are publishing new memory hot-remove support for arm64 memory hotplug,
which complements our initial hot-add patch.
For convenience, we are reposting in a single thread all the 5 patches
that compose the full memory hot-plug support, which are:
- The initial patchset by Scott Branden, orginally released in [2]
(2 patches).
- A second version of our hot-add patch, originally released in [1]
(1 patch).
- New hot-remove support complementing the hot-add patch. (2 patches).
The patches should apply cleanly on Linux 4.11-rc6
(commit: 39da7c509acff13fc8cb12ec1bb20337c988ed36).
We have performed tests and experiments on physical and emulated boards
and we are collecting results (along with more information) at the public
Web page at [3].
Any comments or feedback are, as usual, very much appreciated.
[1] https://lkml.org/lkml/2016/12/14/188
[2] https://lkml.org/lkml/2016/12/1/811
[3] https://hotplug-tests.eu-gb.mybluemix.net
Andrea Reale (2):
Hot-remove implementation for arm64
Add "remove" probe driver for memory hot-remove
Maciej Bielski (1):
Memory hotplug support for arm64 platform (v2)
Scott Branden (2):
arm64: memory-hotplug: Add MEMORY_HOTPLUG, MEMORY_HOTREMOVE,
MEMORY_PROBE
arm64: defconfig: enable MEMORY_HOTPLUG config options
arch/arm64/Kconfig | 11 ++
arch/arm64/configs/defconfig | 3 +
arch/arm64/include/asm/mmu.h | 7 +
arch/arm64/include/asm/pgtable.h | 15 ++
arch/arm64/mm/init.c | 113 +++++++++++
arch/arm64/mm/mmu.c | 417 +++++++++++++++++++++++++++++++++++++++
drivers/base/memory.c | 34 +++-
include/linux/memblock.h | 1 +
mm/memblock.c | 10 +
9 files changed, 610 insertions(+), 1 deletion(-)
--
1.9.1
next reply other threads:[~2017-04-11 14:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 14:54 Andrea Reale [this message]
2017-04-11 14:54 ` [PATCH 1/5] arm64: memory-hotplug: Add MEMORY_HOTPLUG, MEMORY_HOTREMOVE, MEMORY_PROBE Andrea Reale
2017-04-12 0:20 ` kbuild test robot
2017-04-11 14:54 ` [PATCH 2/5] arm64: defconfig: enable MEMORY_HOTPLUG config options Andrea Reale
2017-04-11 14:55 ` [PATCH 3/5] Memory hotplug support for arm64 platform (v2) Andrea Reale
2017-04-11 15:58 ` Mark Rutland
2017-04-24 16:44 ` Maciej Bielski
2017-04-24 17:35 ` Maciej Bielski
2017-04-11 14:55 ` [PATCH 4/5] Hot-remove implementation for arm64 Andrea Reale
2017-04-11 17:12 ` Mark Rutland
2017-04-14 14:01 ` Andrea Reale
2017-04-18 18:21 ` Mark Rutland
2017-04-18 18:48 ` Ard Biesheuvel
2017-04-19 15:53 ` Laura Abbott
2017-04-21 10:05 ` Andrea Reale
2017-04-24 23:59 ` Laura Abbott
2017-04-21 10:02 ` Andrea Reale
2017-04-11 14:56 ` [PATCH 5/5] Add "remove" probe driver for memory hot-remove Andrea Reale
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=cover.1491920513.git.ar@linux.vnet.ibm.com \
--to=ar@linux.vnet.ibm.com \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.bielski@virtualopensystems.com \
--cc=qiuxishi@huawei.com \
--cc=scott.branden@broadcom.com \
--cc=will.deacon@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).