Re: [PATCH v3 0/3] ACPI: container hot remove support.

[Tang Chen]

Hi Yinghai,

How do you think the 1st patch ? Is the idea OK with you ?

And about the memory hotplug thing, so far as I know, we are trying to
limit kernel memory in some nodes, and only support to hot-remove the
nodes with out kernel memory. This functionality is called
online_movable. And some of the patches are already in next-tree, most
of the patches are under review. :)

Thanks. :)

On 11/01/2012 12:48 AM, Yinghai Lu wrote:
> 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-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/