On 2012/11/27 10:38, Tang Chen wrote:
> On 11/27/2012 09:08 AM, Hanjun Guo wrote:
>> On 2012/11/26 14:06, Tang Chen wrote:
>>> On 11/26/2012 01:42 PM, Hanjun Guo wrote:
Hi all,
I think Yasuaki mentioned the key point for the container device remove,
that is dependency.
On 2012/11/27 10:38, Tang Chen wrote:
On 11/27/2012 09:08 AM, Hanjun Guo wrote:
On 2012/11/26 14:06, Tang Chen wrote:
On 11/26/2012 01:42 PM, Hanjun Guo wrote:
Hi all,
I think Yasuaki mentioned the key point for the container device remove,
that is dependency.
Currently, container,
On 11/27/2012 09:08 AM, Hanjun Guo wrote:
On 2012/11/26 14:06, Tang Chen wrote:
On 11/26/2012 01:42 PM, Hanjun Guo wrote:
Hi all,
I think Yasuaki mentioned the key point for the container device remove,
that is dependency.
Currently, container, processor, and memory hotpulg are managed by
On 2012/11/26 14:06, Tang Chen wrote:
> On 11/26/2012 01:42 PM, Hanjun Guo wrote:
>>
>> Hi all,
>> I think Yasuaki mentioned the key point for the container device remove,
>> that is dependency.
>>
>> Currently, container, processor, and memory hotpulg are managed by different
>> ACPI
>> hotplug
On 2012/11/26 14:06, Tang Chen wrote:
> On 11/26/2012 01:42 PM, Hanjun Guo wrote:
>>
>> Hi all,
>> I think Yasuaki mentioned the key point for the container device remove,
>> that is dependency.
>>
>> Currently, container, processor, and memory hotpulg are managed by different
>> ACPI
>> hotplug
On 2012/11/26 14:06, Tang Chen wrote:
On 11/26/2012 01:42 PM, Hanjun Guo wrote:
Hi all,
I think Yasuaki mentioned the key point for the container device remove,
that is dependency.
Currently, container, processor, and memory hotpulg are managed by different
ACPI
hotplug drivers, the
On 2012/11/26 14:06, Tang Chen wrote:
On 11/26/2012 01:42 PM, Hanjun Guo wrote:
Hi all,
I think Yasuaki mentioned the key point for the container device remove,
that is dependency.
Currently, container, processor, and memory hotpulg are managed by different
ACPI
hotplug drivers, the
On 11/27/2012 09:08 AM, Hanjun Guo wrote:
On 2012/11/26 14:06, Tang Chen wrote:
On 11/26/2012 01:42 PM, Hanjun Guo wrote:
Hi all,
I think Yasuaki mentioned the key point for the container device remove,
that is dependency.
Currently, container, processor, and memory hotpulg are managed by
On 11/26/2012 01:42 PM, Hanjun Guo wrote:
Hi all,
I think Yasuaki mentioned the key point for the container device remove,
that is dependency.
Currently, container, processor, and memory hotpulg are managed by different
ACPI
hotplug drivers, the driver works when handle device hotplug
On 2012/10/31 19:09, Yasuaki Ishimatsu wrote:
> Hi Tang,
>
> 2012/10/31 16:27, Tang Chen wrote:
>> Hi,
>>
>> The container hotplug handler container_notify_cb() didn't implement
>> the hot-remove functionality. So, these 3 patches implement it like
>> the following way:
>>
>> patch 1. Do not use
On 2012/10/31 19:09, Yasuaki Ishimatsu wrote:
Hi Tang,
2012/10/31 16:27, Tang Chen wrote:
Hi,
The container hotplug handler container_notify_cb() didn't implement
the hot-remove functionality. So, these 3 patches implement it like
the following way:
patch 1. Do not use
On 11/26/2012 01:42 PM, Hanjun Guo wrote:
Hi all,
I think Yasuaki mentioned the key point for the container device remove,
that is dependency.
Currently, container, processor, and memory hotpulg are managed by different
ACPI
hotplug drivers, the driver works when handle device hotplug
On 11/01/2012 12:48 AM, Yinghai Lu wrote:
> On Wed, Oct 31, 2012 at 4:09 AM, Yasuaki Ishimatsu
> 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
On 11/01/2012 12:48 AM, Yinghai Lu wrote:
On Wed, Oct 31, 2012 at 4:09 AM, Yasuaki Ishimatsu
isimatu.yasu...@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
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
On 10/31/2012 07:09 PM, Yasuaki Ishimatsu wrote:
> Hi Tang,
>
> 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
On Wed, Oct 31, 2012 at 4:09 AM, Yasuaki Ishimatsu
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
Hi Tang,
2012/10/31 16:27, Tang Chen wrote:
> Hi,
>
> The container hotplug handler container_notify_cb() didn't implement
> the hot-remove functionality. So, these 3 patches implement it like
> the following way:
>
> patch 1. Do not use kacpid_wq/kacpid_notify_wq to handle container hotplug
>
Hi,
The container hotplug handler container_notify_cb() didn't implement
the hot-remove functionality. So, these 3 patches implement it like
the following way:
patch 1. Do not use kacpid_wq/kacpid_notify_wq to handle container hotplug
event,
use kacpi_hotplug_wq instead to avoid
Hi,
The container hotplug handler container_notify_cb() didn't implement
the hot-remove functionality. So, these 3 patches implement it like
the following way:
patch 1. Do not use kacpid_wq/kacpid_notify_wq to handle container hotplug
event,
use kacpi_hotplug_wq instead to avoid
Hi Tang,
2012/10/31 16:27, Tang Chen wrote:
Hi,
The container hotplug handler container_notify_cb() didn't implement
the hot-remove functionality. So, these 3 patches implement it like
the following way:
patch 1. Do not use kacpid_wq/kacpid_notify_wq to handle container hotplug
event,
On Wed, Oct 31, 2012 at 4:09 AM, Yasuaki Ishimatsu
isimatu.yasu...@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
On 10/31/2012 07:09 PM, Yasuaki Ishimatsu wrote:
Hi Tang,
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
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
24 matches
Mail list logo
