de 7 PXM 1 [mem 0x8-0xf]
---
Thanks,
Yasuaki Ishimatsu
Any time you
make the user go off and do some tedious calculation that the computer
should have done for them is user-abuse.
-Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
t
of acpi_bus_trim() (all callers pass 1 in there
anyway.
[4/5] Reimplement acpi_bus_trim() using acpi_walk_namespace().
[3/5] Make acpi_bus_trim() carry out two passes as described above.
Acked-by: Yasuaki Ishimatsu
I'm aware of the fact that this will conflict with the patches
Hi Tang,
2012/12/26 16:39, Tang Chen wrote:
> On 12/26/2012 02:53 PM, Yasuaki Ishimatsu wrote:
>> Hi Tang,
>>
>> I don't think it can work well.
>> The patch gets memory range of hotpluggable memory by
>> acpi_numa_memory_affinity_init(). But it too late.
boot option does not work well.
Thanks,
Yasuaki Ishimatsu
2012/12/19 18:11, Tang Chen wrote:
> The Hot Plugable bit in SRAT flags specifys if the memory range
> could be hotplugged.
>
> If user specified movablecore_map=nn[KMG]@ss[KMG], reset
> movablecore_map.map to the intersection of
atures so it's not a common
solution for all architectures.
I agree with you. If BIOS and hardware support memory hotplug, OS should
use them. But if OS cannot use them, we need to solve in OS. I think
that our proposal which used ZONE_MOVABLE is first step for supporting
memory hotplug.
T
In this case, the page used as PT/PMD can be freed.
By the way, why is 0xFD?
There is no reason. I just filled the page with unique number.
Thanks,
Yasuaki Ishimatsu
+ }
+ }
+
+ free_pte_table(pmd);
+ __flush_tlb_all();
+}
+
+static void vmemmap_pmd_remove(pud_t
2012/11/29 6:47, Yinghai Lu wrote:
> So make init_memory_mapping smaller and readable.
>
> -v2: use 0 instead of nr_range as input parameter found by Yasuaki Ishimatsu.
>
> Suggested-by: Ingo Molnar
> Signed-off-by: Yinghai Lu
> Reviewed-by: Pekka Enberg
> Reviewed-b
een added, or a broken
node removed the values would be stale.
I don't think so. Even if we hot add/remove node, the memory range of
each memory device is not changed. So we don't need to change the boot
option.
Thanks,
Yasuaki Ishimatsu
-Tony
--
To unsubscribe from this list: s
atches are only this patch-set. So we hope that this patch-set
is merged into v3.8.
In merging this patch-set into v3.8, Linux on x86_64 makes a memory hot plug
possible.
Thanks,
Yasuaki Ishimatsu
If you want to know the reason, please read following thread.
https://lkml.org/lkml/2012/10/2
is correctly set at hotplug.
But memory range is set by firmware and not changed. So if we set node2
as movable node by movablecore_map, the issue does not occur.
Thanks,
Yasuaki Ishimatsu
-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
t
* sizeof(struct page))
>> PAGE_SHIFT;
- free_map_bootmem(memmap_page, nr_pages);
+ free_map_bootmem(memmap, nr_pages);
}
}
Reviewed-by: Yasuaki Ishimatsu
--
To unsubscribe from this list: send the line "unsubscribe linux
, and fixed them.
So we believe that Linux on x86_64 can support memory hot remove
by the patch-set.
Thanks,
Yasuaki Ishimatsu
2012/11/01 18:44, Wen Congyang wrote:
> The patch-set was divided from following thread's patch-set.
> https://lkml.org/lkml/2012/9/5/201
>
> The las
Hi Tang,
2012/11/21 14:58, Tang Chen wrote:
> Hi Ishimatsu-san,
>
> Thanks for the comments.
>
> And I also found the some algorithm problems in patch2 ~ patch3.
> I am working on it, and a v2 patchset is coming soon. :)
O.K.
I'm waiting nwe patch-set.
Thanks,
Yasuaki
Hi Tang,
When I applied the patch, following error occurred.
mm/page_alloc.c: In function ‘insert_movablecore_map’:
mm/page_alloc.c:5061: error: label ‘out’ used but not defined
Thanks,
Yasuaki Ishimatsu
2012/11/19 23:27, Tang Chen wrote:
> This patch adds functions to parse movablecore_
Hi Tang,
2012/11/19 23:27, Tang Chen wrote:
> From: Yasuaki Ishimatsu
>
> If system can create movable node which all memory of the
> node is allocated as ZONE_MOVABLE, setup_node_data() cannot
> allocate memory for the node's pg_data_t.
> So when memblock_alloc_nid()
t; + pos_end--;
> + break;
> + }
> + }
> + if (pos_end == movablecore_map.nr_map && merge)
> + pos_end--;
> +
> + if (pos_start == movablecore_map.nr_map)
> + merge = fa
Hi Jaegeuk,
2012/11/20 20:25, Jaegeuk Hanse wrote:
On 11/20/2012 07:07 PM, Yasuaki Ishimatsu wrote:
2012/11/20 5:53, Andrew Morton wrote:
On Mon, 19 Nov 2012 22:27:21 +0800
Tang Chen wrote:
This patchset provide a boot option for user to specify ZONE_MOVABLE memory
map for each node in the
the user can select which memory
to use as movable memory easily.
Thanks,
Yasuaki Ishimatsu
The amount of manual system configuration in this proposal looks quite
high. Adding kernel boot parameters really is a last resort. Why was
it unavoidable here?
--
To unsubscribe from this list: send t
Christoph Lameter
> Cc: Minchan Kim
> CC: Andrew Morton
> CC: KOSAKI Motohiro
> CC: Yasuaki Ishimatsu
> Signed-off-by: Wen Congyang
> ---
> drivers/acpi/acpi_memhotplug.c | 8 +-
> include/linux/memory_hotplug.h | 2 +-
> mm/memory_hotplug.c| 5
Hi Rafael,
Please merge this patch into your tree.
It has been acked by Len.
Thanks,
Yasuaki Ishimatsu
2012/11/13 16:30, Yasuaki Ishimatsu wrote:
> Hi Rafael,
>
> The patch was rebased on linux-next. Ant it has been acked by Len:
>
> https://lkml.org/lkml/2012/10/10/65
>
&g
Hi Rafael,
2012/11/16 10:28, Rafael J. Wysocki wrote:
On Friday, November 16, 2012 10:07:49 AM Yasuaki Ishimatsu wrote:
Hi Rafael,
2012/11/16 9:28, Rafael J. Wysocki wrote:
On Thursday, November 15, 2012 02:59:30 PM Wen Congyang wrote:
The memory device can be removed by 2 ways:
1. send
e driver is loaded
Yasuaki Ishimatsu (1):
acpi,memory-hotplug : add memory offline code to
acpi_memory_device_remove()
Well, I have tried _really_ hard to apply this patchset, but pretty much
none of the patches except for [1/7] applied for me. I have no idea what
tree they are against,
ovable-dedicated node
>memory_hotplug: allow online/offline memory to result movable node
>
> drivers/base/node.c | 6 ++
> include/linux/nodemask.h | 4
> mm/Kconfig | 8
> mm/memory_hotplug.c | 16 ++++
> mm/page_
ture to bind such device when the driver is being
> loaded.
>
> CC: David Rientjes
> CC: Jiang Liu
> CC: Len Brown
> CC: Benjamin Herrenschmidt
> CC: Paul Mackerras
> CC: Christoph Lameter
> Cc: Minchan Kim
> CC: Andrew Morton
> CC: KOSAKI Motohiro
> CC:
low that the device can be bound when the
> driver is being loaded.
>
> CC: David Rientjes
> CC: Jiang Liu
> CC: Len Brown
> CC: Benjamin Herrenschmidt
> CC: Paul Mackerras
> CC: Christoph Lameter
> Cc: Minchan Kim
> CC: Andrew Morton
> CC: KOSAKI Moto
> CC: Christoph Lameter
> Cc: Minchan Kim
> CC: Andrew Morton
> CC: KOSAKI Motohiro
> CC: Yasuaki Ishimatsu
> CC: Rafael J. Wysocki
> CC: Konrad Rzeszutek Wilk
> Signed-off-by: Wen Congyang
> ---
Reviewed-by: Yasuaki Ishimatsu
Thanks,
Yasuaki
t;
> CC: David Rientjes
> CC: Jiang Liu
> CC: Len Brown
> CC: Benjamin Herrenschmidt
> CC: Paul Mackerras
> CC: Christoph Lameter
> Cc: Minchan Kim
> CC: Andrew Morton
> CC: KOSAKI Motohiro
> CC: Yasuaki Ishimatsu
> CC: Rafael J. Wysocki
> CC: K
er
> Cc: Minchan Kim
> CC: Andrew Morton
> CC: KOSAKI Motohiro
> CC: Yasuaki Ishimatsu
> CC: Rafael J. Wysocki
> CC: Konrad Rzeszutek Wilk
> Signed-off-by: Wen Congyang
> ---
Reviewed-by: Yasuaki Ishimatsu
Thanks,
Yasuaki Ishimatsu
> drivers/acpi/acpi_memhotplug
_remove()
> which is protected by device_lock().
>
> CC: David Rientjes
> CC: Jiang Liu
> CC: Len Brown
> CC: Benjamin Herrenschmidt
> CC: Paul Mackerras
> CC: Christoph Lameter
> Cc: Minchan Kim
> CC: Andrew Morton
> CC: KOSAKI Motohiro
> CC: Ya
the system.
The patch creates "sun" file in sysfs for identifying physical position
of the slot.
Reviewed-by: Toshi Kani
Signed-off-by: Yasuaki Ishimatsu
---
Documentation/ABI/testing/sysfs-devices-sun | 14 ++
drivers/acpi/scan.c
> +{
> + struct map_range mr[NR_RANGE_MR];
> + unsigned long ret = 0;
> + int nr_range, i;
> +
> + pr_info("init_memory_mapping: [mem %#010lx-%#010lx]\n",
> +start, end - 1);
> +
> + memset(mr, 0, sizeof(mr));
> + nr_range =
o 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
Thanks,
Yasuaki Ishima
Hi Greg,
2012/10/27 0:25, Greg Kroah-Hartman wrote:
On Fri, Oct 26, 2012 at 04:33:49PM +0900, Yasuaki Ishimatsu wrote:
Hi Greg,
Sorry for late reply.
2012/10/20 2:59, Greg Kroah-Hartman wrote:
On Fri, Oct 19, 2012 at 06:29:52AM +0200, Rafael J. Wysocki wrote:
On Thursday 11 of October 2012
kernelcore_max_addr [PATCH 19 - 25]
- Bug fix [PATCH 26]
Why don't you separate the patch-set into each feature development?
By separating the patch-set, many people can easily participate
in your development.
Thanks,
Yasuaki Ishimatsu
2012/10/30 0:07, Lai Jiangshan wrote:
> Movable memory is a very i
pu.
But in this case, it should return error number since some process may run on
the cpu. If the cpu has a running process and the cpu is turned the power off,
the system may not work well.
Reviewed-by: Srivatsa S. Bhat
Reviewed-by: Toshi Kani
Signed-off-by: Yasuaki Ishimatsu
---
drivers
Hi Greg,
Sorry for late reply.
2012/10/20 2:59, Greg Kroah-Hartman wrote:
On Fri, Oct 19, 2012 at 06:29:52AM +0200, Rafael J. Wysocki wrote:
On Thursday 11 of October 2012 19:12:28 Yasuaki Ishimatsu wrote:
acpi_bus_trim() stops removing devices, when acpi_bus_remove() return error
number
Hi Tang,
2012/10/24 16:24, Tang Chen wrote:
> On 10/24/2012 02:54 PM, Yasuaki Ishimatsu wrote:
>> Hi Tang,
>>
>> 2012/10/24 15:05, Tang Chen wrote:
>>> As the comments in __acpi_os_execute() said:
>>>
>>> We can't run hotplug code in keve
-> __acpi_os_execute(type, function, context, 0)
>
> The last parameter 0 makes the container_notify_cb() executed in
> kacpi_notify_wq or kacpid_wq. So, we need to put the real hotplug code
> into kacpi_hotplug_wq.
I cannot understand the purpose of the patch.
Is the patch a bug fix p
the HOTREMOVE guard.
>
> Signed-off-by: Michal Hocko
> Cc: David Rientjes
> Cc: Jiang Liu
> Cc: Len Brown
> Cc: Benjamin Herrenschmidt
> Cc: Paul Mackerras
> Cc: Christoph Lameter
> Cc: Minchan Kim
> Cc: KOSAKI Motohiro
> Cc: Yasuaki Ishimatsu
Looks go
CCing Rafael, because he become ACPI Maintainer.
Hi Wen,
If you update the patch-set, please CCing Rafael from the next time.
Thanks,
Yasuaki Ishimatsu
2012/10/19 19:03, we...@cn.fujitsu.com wrote:
> From: Wen Congyang
>
> The patch-set implements a framework for hot removi
2012/10/19 17:45, Wen Congyang wrote:
> At 10/19/2012 04:19 PM, Yasuaki Ishimatsu Wrote:
>> 2012/10/19 17:06, Yasuaki Ishimatsu wrote:
>>> Hi Wen,
>>>
>>> Some bug fix patches have been merged into linux-next.
>>> So the patches confuse me.
>
>
2012/10/19 17:06, Yasuaki Ishimatsu wrote:
> Hi Wen,
>
> Some bug fix patches have been merged into linux-next.
> So the patches confuse me.
The following patches have been already merged into linux-next
and mm-tree as long as I know.
>> Wen Congyang (6):
>> c
Hi Wen,
Some bug fix patches have been merged into linux-next.
So the patches confuse me.
Why did you send same patches again?
Thanks,
Yasuaki Ishimatsu
2012/10/19 15:46, we...@cn.fujitsu.com wrote:
> From: Wen Congyang
>
> Changes from v2 to v3:
>Merge the bug fix from ishim
Hi Rafael,
2012/10/19 10:06, Rafael J. Wysocki wrote:
On Friday 28 of September 2012 19:36:02 Yasuaki Ishimatsu wrote:
Even if cpu_down() fails, acpi_processor_remove() continues to remove the cpu.
But in this case, it should return error number since some process may run on
the cpu. If the
Hi Kosaki,
Sorry for late reply.
2012/10/13 4:28, KOSAKI Motohiro wrote:
On Thu, Oct 4, 2012 at 10:32 PM, Yasuaki Ishimatsu
wrote:
The function get_page_bootmem() may be called more than one time to the same
page. There is no need to set page's type, private if the function is not
the
, it's my mistake.
Could you update it in next version?
Thanks,
Yasuaki Ishimatsu
Thanks
Wen Congyang
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org
hout
> using this lockable flag.
>
> Signed-off-by: Toshi Kani
Looks good to me.
Reviewed-by: Yasuaki Ishimatsu
> ---
> drivers/acpi/scan.c | 5 -
> include/acpi/acpi_bus.h | 3 +--
> 2 files changed, 1 insertion(+), 7 deletions(-)
>
> diff --git a/dr
;
> The flags.lockable indicates whether or not this ACPI object
> implements _LCK method. Fix the stable pointer access by replacing
> it with acpi_get_handle() to check if _LCK is implemented.
>
> Signed-off-by: Toshi Kani
Looks good to me.
Reviewed-by: Yasuaki Ishimatsu
> ---
x27;err:' label
and there leave the function and let 'physical_node' go out of scope
and leak the memory we allocated.
This patch fixes the leak by simply freeing the unused/unneeded memory
pointed to by 'physical_node' just before we jump to 'err:'.
Signe
tainer_device_ids;
> + container_id->id[0]; container_id++) {
> + if (!strcmp((char *)container_id->id, hid))
> + break;
> }
> + if (!container_id->id[0])
> + goto end;
How about prepare is_container_device() function a
register_node() is defined as extern in include/linux/node.h. But the function
is only called from register_one_node() in driver/base/node.c.
So the patch defines register_node() as static.
CC: David Rientjes
CC: Andrew Morton
Signed-off-by: Yasuaki Ishimatsu
---
drivers/base/node.c |2
Hi Toshi,
2012/10/11 22:58, Toshi Kani wrote:
On Thu, 2012-10-11 at 19:12 +0900, Yasuaki Ishimatsu wrote:
acpi_bus_trim() stops removing devices, when acpi_bus_remove() return error
number. But acpi_bus_remove() cannot return error number correctly.
acpi_bus_remove() only return -EINVAL, when
2012/10/12 5:31, David Rientjes wrote:
On Thu, 11 Oct 2012, Yasuaki Ishimatsu wrote:
When calling unregister_node(), the function shows following message at
device_release().
"Device 'node2' does not have a release() function, it is broken and must
be fixed."
The rea
ice. But I think there is no impact with the
exceptionof CPU and Memory hotplug path. Because other device also fails
but the fail is an irregular case like device is NULL.
v1->v2
- add a rollback for reinstalling a notify handler.
Signed-off-by: Yasuaki Ishimatsu
---
drivers/acpi/sca
2012/10/06 4:36, KOSAKI Motohiro wrote:
On Thu, Oct 4, 2012 at 10:26 PM, Yasuaki Ishimatsu
wrote:
When (hot)adding memory into system, /sys/firmware/memmap/X/{end, start, type}
sysfs files are created. But there is no code to remove these files. The patch
implements the function to remove them
Hi Toshi,
2012/10/10 22:01, Toshi Kani wrote:
On Wed, 2012-10-10 at 10:07 +0900, Yasuaki Ishimatsu wrote:
:
if (acpi_drv) {
if (acpi_drv->ops.notify)
acpi_device_remove_notify_handler(acpi_dev);
THIS CALL
- if (acpi_
tem reuses the node struct, it has a garbage.
CC: David Rientjes
CC: Jiang Liu
Cc: Minchan Kim
CC: Andrew Morton
CC: KOSAKI Motohiro
Signed-off-by: Yasuaki Ishimatsu
Signed-off-by: Wen Congyang
---
drivers/base/node.c | 11 +++
1 file changed, 11 insertions(+)
Index:
u
Cc: Minchan Kim
CC: Andrew Morton
CC: KOSAKI Motohiro
CC: Wen Congyang
Signed-off-by: Yasuaki Ishimatsu
---
drivers/base/memory.c |9 -
1 file changed, 8 insertions(+), 1 deletion(-)
Index: linux-3.6/drivers/base/memory.c
This patch-set is patches to which [1] and [2] are updated
[1] memory-hotplug: add memory_block_release
[2] memory-hotplug: add node_device_release
from following patch-set.
https://lkml.org/lkml/2012/9/27/39
So the patch-set version is v2.
v1 -> v2
[PATCH 1/2]
- change subject to Suppress "
Hi Len,
How about v5 patch?
Thanks,
Yasuaki Ishimatsu
2012/10/09 15:49, Yasuaki Ishimatsu wrote:
> _SUN method provides the slot unique-ID in the ACPI namespace. And The value
> is written in Advanced Configuration and Power Interface Specification as
> follows:
>
> &qu
wed-by: Yasuaki Ishimatsu
Thanks,
Yasuaki Ishimatsu
> drivers/acpi/dock.c | 26 +++---
> 1 files changed, 7 insertions(+), 19 deletions(-)
>
> diff --git a/drivers/acpi/dock.c b/drivers/acpi/dock.c
> index 88eb143..ae4ebf2 100644
> --- a/drivers/acpi/d
Hi Toshi,
2012/10/10 1:36, Toshi Kani wrote:
On Tue, 2012-10-09 at 17:48 +0900, Yasuaki Ishimatsu wrote:
acpi_bus_trim() stops removing devices, when acpi_bus_remove() return error
number. But acpi_bus_remove() cannot return error number correctly.
acpi_bus_remove() only return -EINVAL, when
return ret;
}
I believe the error to be fixed with this patch.
Could you try it?
Thanks,
Yasuaki Ishimatsu
and this patch never
appeared in linux-next before being merged. :-(
It was first sighted October 3.
I have reverted that commit for today.
If
ice. But I think there is no impact with the
exceptionof CPU and Memory hotplug path. Because other device also fails
but the fail is an irregular case like device is NULL.
Signed-off-by: Yasuaki Ishimatsu
---
drivers/acpi/scan.c| 15 ---
drivers/base/dd.c
Hi Wen,
2012/10/09 17:02, Wen Congyang wrote:
Hi, ishimatsu:
At 07/12/2012 07:28 PM, Yasuaki Ishimatsu Wrote:
acpi_bus_trim() stops removing devices, when acpi_bus_remove() return error
number. But acpi_bus_remove() cannot return error number correctly.
acpi_bus_remove() only return -EINVAL
umber printed on
the physical slot whenever possible."
So if we can know the value, we can identify the physical position of the
slot in the system.
The patch creates "sun" file in sysfs for identifying physical position
of the slot.
Reviewed-by: Toshi Kani
Signed-off-b
Hi Len,
2012/10/09 14:05, Len Brown wrote:
> On 10/08/2012 07:57 PM, Yasuaki Ishimatsu wrote:
>> Hi Len,
>>
>> What should I do to put this patch in your tree?
>
> Please add a description of the attribute in
> Documentation/ABI/testing/
>
> A human needs t
Hi Len,
What should I do to put this patch in your tree?
Thanks,
Yasuaki Ishimatsu
2012/10/03 18:54, Yasuaki Ishimatsu wrote:
> Hi Len,
>
> Ping...
> Pleae merge the patch into your tree.
>
> Thanks,
> Yasuaki Ishimatsu
>
> 2012/09/24 11:31, Yasuaki Ishimatsu w
tplug writer. So, add a WARN_ON() in put_online_cpus() to detect such cases
where the refcount can go negative, and also attempt to fix it up, so that we
can
continue to run.
Signed-off-by: Srivatsa S. Bhat
---
Looks good to me.
Reviewed-by: Yasuaki Ishimatsu
kernel/cpu.c |4
1 fi
: Christoph Lameter
Cc: Minchan Kim
CC: Andrew Morton
CC: KOSAKI Motohiro
CC: Yasuaki Ishimatsu
Signed-off-by: Wen Congyang
---
mm/memory_hotplug.c | 54
1 file changed, 54 insertions(+)
Index: linux-3.6/mm/memory_hotplug.c
ph Lameter
Cc: Minchan Kim
CC: Andrew Morton
CC: KOSAKI Motohiro
Signed-off-by: Yasuaki Ishimatsu
Signed-off-by: Wen Congyang
---
mm/memory_hotplug.c | 207
1 file changed, 207 insertions(+)
Index: linux-3.6/mm/memory
Motohiro
CC: Yasuaki Ishimatsu
Signed-off-by: Wen Congyang
---
arch/x86/include/asm/pgtable_types.h |1
arch/x86/mm/init_64.c| 147 +++
arch/x86/mm/pageattr.c | 47 +--
3 files changed, 173 insertions(+), 22 deletions
: Yasuaki Ishimatsu
---
arch/ia64/mm/discontig.c |8 +++
arch/powerpc/mm/init_64.c |8 +++
arch/s390/mm/vmem.c |8 +++
arch/sparc/mm/init_64.c |8 +++
arch/x86/mm/init_64.c | 119 ++
include/linux/mm.h|2
mm
implemented for ia64, ppc, s390,
and sparc.
CC: David Rientjes
CC: Jiang Liu
CC: Len Brown
CC: Christoph Lameter
Cc: Minchan Kim
CC: Andrew Morton
CC: KOSAKI Motohiro
Signed-off-by: Wen Congyang
Signed-off-by: Yasuaki Ishimatsu
---
arch/ia64/mm/discontig.c |6
arch/powerpc/mm
: Len Brown
CC: Christoph Lameter
Cc: Minchan Kim
CC: Andrew Morton
CC: KOSAKI Motohiro
CC: Wen Congyang
Signed-off-by: Yasuaki Ishimatsu
---
mm/memory_hotplug.c | 15 +++
1 file changed, 11 insertions(+), 4 deletions(-)
Index: linux-3.6/mm/memory_hotp
Kim
CC: Andrew Morton
CC: KOSAKI Motohiro
CC: Wen Congyang
Signed-off-by: Yasuaki Ishimatsu
---
mm/memory_hotplug.c | 13 -
1 file changed, 8 insertions(+), 5 deletions(-)
Index: linux-3.6/mm/memory_hotplug.c
w how to implement it for s390).
CC: David Rientjes
CC: Jiang Liu
CC: Len Brown
CC: Benjamin Herrenschmidt
CC: Paul Mackerras
CC: Christoph Lameter
Cc: Minchan Kim
CC: Andrew Morton
CC: KOSAKI Motohiro
CC: Yasuaki Ishimatsu
Signed-off-by: Wen Congyang
---
arch/ia64/mm/init.c|
is allocated by bootmem.
CC: David Rientjes
CC: Jiang Liu
CC: Len Brown
CC: Christoph Lameter
Cc: Minchan Kim
CC: Andrew Morton
CC: KOSAKI Motohiro
Signed-off-by: Wen Congyang
Signed-off-by: Yasuaki Ishimatsu
---
drivers/firmware/memmap.c| 98
: KOSAKI Motohiro
Signed-off-by: Wen Congyang
Signed-off-by: Yasuaki Ishimatsu
---
drivers/base/memory.c | 39 +++
include/linux/memory.h |5 +
mm/memory_hotplug.c| 17 +++--
3 files changed, 59 insertions(+), 2 deletions(-)
Index
The patch-set was divided from following thread's patch-set.
https://lkml.org/lkml/2012/9/5/201
If you want to know the reason, please read following thread.
https://lkml.org/lkml/2012/10/2/83
The patch-set has only the function of kernel core side for physical
memory hot remove. So if you use
Hi Kosaki-san,
2012/10/02 3:12, KOSAKI Motohiro wrote:
On Mon, Oct 1, 2012 at 2:54 AM, Yasuaki Ishimatsu
wrote:
Hi Kosaki-san,
2012/09/29 7:19, KOSAKI Motohiro wrote:
I don't understand it. How can we get rid of the warning?
See cpu_device_release() for example.
If we implem
Hi Chen,
Sorry for late reply.
2012/10/02 13:21, Ni zhan Chen wrote:
On 09/05/2012 05:25 PM, we...@cn.fujitsu.com wrote:
From: Yasuaki Ishimatsu
All pages of virtual mapping in removed memory cannot be freed, since some pages
used as PGD/PUD includes not only removed memory but also other
From: Wen Congyang
The memory device has been ejected and powoffed, so we can call
acpi_bus_remove() to remove the memory device from acpi bus.
CC: Len Brown
Reviewed-by: Yasuaki Ishimatsu
Signed-off-by: Wen Congyang
---
drivers/acpi/acpi_memhotplug.c |3 ++-
1 file changed, 2
From: Wen Congyang
The function acpi_bus_remove() can remove a acpi device from acpi bus.
When a acpi device is removed, we need to call this function to remove
the acpi device from acpi bus. So export this function.
CC: Len Brown
Reviewed-by: Yasuaki Ishimatsu
Signed-off-by: Wen Congyang
The patch-set was divided from following thread's patch-set.
https://lkml.org/lkml/2012/9/5/201
If you want to know the reason, please read following thread.
https://lkml.org/lkml/2012/10/2/83
The patch exports "acpi_bus_remove()" for removing a acpi device from a
acpi bus at memory hot plug.
Kim
CC: Andrew Morton
CC: KOSAKI Motohiro
CC: Yasuaki Ishimatsu
Signed-off-by: Wen Congyang
Signed-off-by: Yasuaki Ishimatsu
---
drivers/acpi/acpi_memhotplug.c | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
Index: linux-3.6/drivers/acpi/acpi_memhotplug.c
From: Yasuaki Ishimatsu
For hot removing physical memory, the patch adds remove_memory() into
acpi_memory_remove_memory(). But we cannot support physical memory
hot remove. So remove_memory() do nothinig.
CC: David Rientjes
CC: Jiang Liu
CC: Len Brown
CC: Christoph Lameter
Cc: Minchan Kim
From: Yasuaki Ishimatsu
add_memory() hot adds a physical memory. But remove_memory does not
hot remove a phsical memory. It only offlines memory. The name
confuse us.
So the patch renames remove_memory() to offline_memory(). We will
use rename_memory() for hot removing memory.
CC: David
From: Yasuaki Ishimatsu
The memory device can be removed by 2 ways:
1. send eject request by SCI
2. echo 1 >/sys/bus/pci/devices/PNP0C80:XX/eject
In the 1st case, acpi_memory_disable_device() will be called.
In the 2nd case, acpi_memory_device_remove() will be called.
acpi_memory_device_rem
Hi Len,
Ping...
Pleae merge the patch into your tree.
Thanks,
Yasuaki Ishimatsu
2012/09/24 11:31, Yasuaki Ishimatsu wrote:
> Hi Len,
>
> Ping...
> I want you to merge the patch into your tree for linux-3.7.
>
> Thanks,
> Yasuaki Ishimatsu
>
> 2012/08/30 10:34, Yas
We are trying to implement a physical memory hot removing function as
following thread.
https://lkml.org/lkml/2012/9/5/201
But there is not enough review to merge into linux kernel.
I think there are following blockades.
1. no physical memory hot removable system
2. huge patch-set
If you ha
Hi Chen,
2012/10/03 11:12, Ni zhan Chen wrote:
On 10/03/2012 09:21 AM, Yasuaki Ishimatsu wrote:
Hi Andrew,
2012/10/03 6:42, Andrew Morton wrote:
On Tue, 2 Oct 2012 17:25:06 +0900
Yasuaki Ishimatsu wrote:
remove_memory() offlines memory. And it is called by following two cases:
1. echo
Hi Andrew,
2012/10/03 6:42, Andrew Morton wrote:
On Tue, 2 Oct 2012 17:25:06 +0900
Yasuaki Ishimatsu 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 c
2012/10/02 18:42, Ni zhan Chen wrote:
> On 10/02/2012 04:25 PM, Yasuaki Ishimatsu wrote:
>> We are trying to implement a physical memory hot removing function as
>> following thread.
>>
>> https://lkml.org/lkml/2012/9/5/201
>>
>> But there is not enough rev
id Rientjes
CC: Jiang Liu
CC: Len Brown
CC: Christoph Lameter
Cc: Minchan Kim
CC: Andrew Morton
CC: KOSAKI Motohiro
Signed-off-by: Wen Congyang
Signed-off-by: Yasuaki Ishimatsu
---
drivers/base/memory.c | 31 +++
include/linux/memory_hotplug.
Rientjes
CC: Jiang Liu
CC: Len Brown
CC: Christoph Lameter
Cc: Minchan Kim
CC: Andrew Morton
CC: KOSAKI Motohiro
Signed-off-by: Wen Congyang
Signed-off-by: Yasuaki Ishimatsu
---
drivers/base/memory.c |9 +++--
include/linux/memory_hotplug.h |1 +
mm/memory_hotp
We are trying to implement a physical memory hot removing function as
following thread.
https://lkml.org/lkml/2012/9/5/201
But there is not enough review to merge into linux kernel.
I think there are following blockades.
1. no physical memory hot removable system
2. huge patch-set
If you ha
Hi Kosaki-san,
2012/09/29 7:15, KOSAKI Motohiro wrote:
On Thu, Sep 27, 2012 at 11:50 PM, Yasuaki Ishimatsu
wrote:
Hi Chen,
2012/09/28 11:22, Ni zhan Chen wrote:
On 09/05/2012 05:25 PM, we...@cn.fujitsu.com wrote:
From: Yasuaki Ishimatsu
remove_memory() only try to offline pages. It is
Hi Chen,
2012/10/02 8:45, Ni zhan Chen wrote:
On 10/01/2012 12:44 PM, Yasuaki Ishimatsu wrote:
Hi Chen,
2012/09/29 17:19, Ni zhan Chen wrote:
On 09/05/2012 05:25 PM, we...@cn.fujitsu.com wrote:
From: Wen Congyang
This patch series aims to support physical memory hot-remove.
The patches
emulation, memory device will associated to one node or ...?
Memory device has only one node, even if you use numa emulation.
Thanks,
Yasuaki Ishimatsu
CC: David Rientjes
CC: Jiang Liu
CC: Len Brown
CC: Benjamin Herrenschmidt
CC: Paul Mackerras
CC: Christoph Lameter
Cc: Minchan Kim
CC
401 - 500 of 635 matches
Mail list logo
