Skip to content

memory-hotplug : notification of memoty block's state

Yasuaki Ishimatsu linux-acpi linux-mm lkml 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest2 patches 6 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2memory-hotplug : Preparation to notify memory block's state at memory hot removedrivers/base/memory.c include/linux/memory_hotplug.h mm/memory_hotplug.c+15 -80 replies
2/2memory-hotplug : update memory block's state and notfy theinformation to userspacedrivers/base/memory.c include/linux/memory_hotplug.h mm/memory_hotplug.c+61 -50 replies

Reviews trailers per patch

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

Read the v1 thread

Cover letter [PATCH 0/2] memory-hotplug : notification of memoty block's state

We are trying to implement a physical memory hot removing function as following thread.

https://lkml.org/lkml/2012/9/5/201

But there is not enough review to merge into linux kernel.

I think there are following blockades.
1. no physical memory hot removable system
2. huge patch-set

If you have a KVM system, we can get rid of 1st blockade. Because applying following patch, we can create memory hot removable system on KVM guest.

http://lists.gnu.org/archive/html/qemu-devel/2012-07/msg01389.html

2nd blockade is own problem. So we try to divide huge patch into a small patch in each function as follows:

- bug fix
- acpi framework
- kernel core

We had already sent bug fix patches.

https://lkml.org/lkml/2012/9/27/39

And the patch fixes following bug.

remove_memory() offlines memory. And it is called by following two cases:

1. echo offline >/sys/devices/system/memory/memoryXX/state
2. hot remove a memory device

In the 1st case, the memory block's state is changed and the notification that memory block's state changed is sent to userland after calling offline_memory(). So user can notice memory block is changed.

But in the 2nd case, the memory block's state is not changed and the notification is not also sent to userspcae even if calling offline_memory(). So user cannot notice memory block is changed.

We should also notify to userspace at 2nd case.