Correct memory hot add/remove for powerpc
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest8 patches 10 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/8 | register bootmem pages for powerpc when sparse vmemmap is not definedarch/ arch/ mm/ | +16 | 2 replies | |
| 2/8 | Mark powerpc memory resources as busyarch/ | +1 | 3 replies | |
| 3/8 | Add all memory via sysfs probe interface at oncedrivers/ | +6 | 5 replies | |
| 4/8 | Create a sysfs release file for hot removing memoryDocumentation/ arch/ arch/ +1 more | +100 | 0 replies | |
| 5/8 | Add notifiers for memory hot add/removeDocumentation/ include/ mm/ | +51 | 0 replies | |
| 6/8 | Update the powerpc arch specific memory add/remove handlersarch/ arch/ | +29 | 0 replies | |
| 7/8 | Add memory hot add/remove notifier handlers for pwoerpcarch/ | +103 | 0 replies | |
| 8/8 | Remove no longer needed powerpc memory node update handlerarch/ | +8 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/8] Correct memory hot add/remove for powerpc
The current implementation of memory hot add and remove for powerpc is broken. This patch set both corrects this issue and updates the memory hot add and remove code for powerpc so that it can be done properly in the kernel.
The first two patches update the powerpc hot add and remove code to work with all of the updates that have gone in to enable memory remove with sparse vmemmap enabled. With these two patches applied the powerpc code is back to working, but not working properly.
The remaining patches update the powerpc memory add and remove code so the work can be done in the kernel and all while holding the memory hotplug lock. The current powerpc implementation does some of the work in the kernel and some of the work in userspace. While this code did work at one time, it has a problem in that it does part of the work to add and remove memory without holding the memory hotplug lock. In this scheme memory could be added and removed fast enough to cause the system to crash. This was a result of doing part of the add or remove without holding the lock.
In order to do memory hot remove in the kernel, this patch set introduces a sysfs release file (/sys/device/system/memory/release) which one can write the physical address of the memory to be removed to. Additionally there is a new set of flags defined for the memory notification chain to indicate that memory is being hot added or hot removed. This allows any work that may need to be done prior to or after memory is hot added or removed to be performed.
The remaining patches in the patch set update the powerpc to properly do memory hot add and remove in the kernel.
Nathan Fontenot
--- Documentation/memory-hotplug.txt | 26 ++++ arch/powerpc/mm/mem.c | 35 +++++- arch/powerpc/platforms/pseries/hotplug-memory.c | 95 +--------------- drivers/base/memory.c | 81 ++++++++++++-- linux/Documentation/memory-hotplug.txt | 34 ++++- linux/arch/powerpc/Kconfig | 2 linux/arch/powerpc/mm/init_64.c | 6 + linux/arch/powerpc/mm/mem.c | 9 + linux/arch/powerpc/platforms/pseries/dlpar.c | 103 ++++++++++++++++++ linux/arch/powerpc/platforms/pseries/hotplug-memory.c | 60 +--------- linux/arch/x86/Kconfig | 2 linux/drivers/base/memory.c | 20 +-- linux/include/linux/memory.h | 6 + linux/mm/Kconfig | 2 linux/mm/memory_hotplug.c | 25 +++- 15 files changed, 322 insertions(+), 184 deletions(-)
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>