On Tue, 2 Oct 2012 17:25:06 +0900 Yasuaki Ishimatsu <isimatu.yasuaki@xxxxxxxxxxxxxx> wrote: > 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. These two little patches look reasonable to me. There's a lot of recent activity with memory hotplug! We're in the 3.7 merge window now so it is not a good time to be merging new material. Also there appear to be two teams working on it and it's unclear to me how well coordinated this work is? However these two patches are pretty simple and do fix a problem, so I added them to the 3.7 MM queue. -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
