lkml.org 
[lkml]   [2012]   [Oct]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    SubjectRe: [PATCH v3 0/3] ACPI: container hot remove support.
    From
    On Wed, Oct 31, 2012 at 4:09 AM, Yasuaki Ishimatsu
    <isimatu.yasuaki@jp.fujitsu.com> 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


    \
     
     \ /
      Last update: 2012-10-31 18:21    [W:4.083 / U:0.288 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site