On Wed, Oct 31, 2012 at 4:09 AM, Yasuaki Ishimatsu <isimatu.yasuaki@xxxxxxxxxxxxxx> wrote: >> patch 2. Introduce a new function container_device_remove() to handle >> ACPI_NOTIFY_EJECT_REQUEST event for container. > > If container device contains memory device, the function is > very danger. As you know, we are developing a memory hotplug. > If memory has kernel memory, memory hot remove operations fails. > But container_device_remove() cannot realize it. So even if > the memory hot remove operation fails, container_device_remove() > keeps hot remove operation. Finally, the function sends _EJ0 > to firmware. In this case, if the memory is accessed, kernel > panic occurs. > The example is as follows: > > https://lkml.org/lkml/2012/9/26/318 so what is the overall status memory hot-remove? how are following memory get processed ? 1. memory for kernel text, module 2. page table 3. vmemmap 4. memory for kmalloc, for dma -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
