(2014/10/22 1:56), Toshi Kani wrote:
On Mon, 2014-10-20 at 19:05 +0900, Yasuaki Ishimatsu wrote:
:
When hot removing memory, pgdat is set to 0 in try_offline_node().
But if the pgdat is allocated by bootmem allocator, the clearing
step is skipped. And when hot adding the same memory, the
On Mon, 2014-10-20 at 19:05 +0900, Yasuaki Ishimatsu wrote:
:
> When hot removing memory, pgdat is set to 0 in try_offline_node().
> But if the pgdat is allocated by bootmem allocator, the clearing
> step is skipped. And when hot adding the same memory, the uninitialized
> pgdat is reused. But
On Mon, 2014-10-20 at 19:05 +0900, Yasuaki Ishimatsu wrote:
:
When hot removing memory, pgdat is set to 0 in try_offline_node().
But if the pgdat is allocated by bootmem allocator, the clearing
step is skipped. And when hot adding the same memory, the uninitialized
pgdat is reused. But
(2014/10/22 1:56), Toshi Kani wrote:
On Mon, 2014-10-20 at 19:05 +0900, Yasuaki Ishimatsu wrote:
:
When hot removing memory, pgdat is set to 0 in try_offline_node().
But if the pgdat is allocated by bootmem allocator, the clearing
step is skipped. And when hot adding the same memory, the
When hot adding the same memory after hot removing a memory,
the following messages are shown:
WARNING: CPU: 20 PID: 6 at mm/page_alloc.c:4968
free_area_init_node+0x3fe/0x426()
...
Call Trace:
[<...>] dump_stack+0x46/0x58
[<...>] warn_slowpath_common+0x81/0xa0
[<...>]
When hot adding the same memory after hot removing a memory,
the following messages are shown:
WARNING: CPU: 20 PID: 6 at mm/page_alloc.c:4968
free_area_init_node+0x3fe/0x426()
...
Call Trace:
[...] dump_stack+0x46/0x58
[...] warn_slowpath_common+0x81/0xa0
[...] warn_slowpath_null+0x1a/0x20
6 matches
Mail list logo