public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
To: Lai Jiangshan <laijs@cn.fujitsu.com>
Cc: Mel Gorman <mgorman@suse.de>,
	David Rientjes <rientjes@google.com>,
	LKML <linux-kernel@vger.kernel.org>,
	x86 maintainers <x86@kernel.org>,
	Jiang Liu <jiang.liu@huawei.com>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Yinghai Lu <yinghai@kernel.org>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	"'FNST-Wen Congyang'" <wency@cn.fujitsu.com>
Subject: Re: [V4 PATCH 27/27] memory,hotplug: Don't modify the zone_start_pfn outside of zone_span_writelock()
Date: Tue, 11 Sep 2012 19:18:14 +0900	[thread overview]
Message-ID: <504F0FE6.5090709@jp.fujitsu.com> (raw)
In-Reply-To: <504F07ED.3070502@cn.fujitsu.com>

Hi Lai,

2012/09/11 18:44, Lai Jiangshan wrote:
> On 09/11/2012 08:40 AM, Yasuaki Ishimatsu wrote:
>> Hi Lai,
>>
>> Using memory_online to hot-added node's memory, the following kernel messages
>> were shown. Is this a known issue?
>
> Fixed.
>
> Subject: Don't modify the zone_start_pfn outside of zone_span_writelock()
>
> Original __add_zone() and new online_movable/online_kernel
> maybe call sleep-able init_currently_empty_zone() to init wait_table,
>
> but this function also modifies the zone_start_pfn without lock.
> so we move this code out, and ensure the modification of zone_start_pfn is done
> with zone_span_writelock() held or booting.
>
> Since zone_start_pfn is not modified by init_currently_empty_zone()
> grow_zone_span() needs to be updated to be aware of empty zone.
>
> Signed-off-by: Lai Jiangshan <laijs@cn.fujitsu.com>
> Reported-by: Yasuaki ISIMATU <isimatu.yasuaki@jp.fujitsu.com>
> Tested-by: Wen Congyang <wency@cn.fujitsu.com>

Applying the patch, the kernel messages disappeared. Thanks.
But I have a question. Using online_movable, the following messages are shown.

[  608.314608] Built 3 zonelists in Node order, mobility grouping on.  Total pages: 7844412
[  608.411478] Policy zone: Normal

I think memory is allocated to ZONE_MOVABLE by using online_movable.
So why is "Policy zone: Normal" shown? It should be "Policy zone: Movable"

Thanks,
Yasuaki Ishimatsu

> ---
> diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
> index 3ad25f9..c26a4ea 100644
> --- a/mm/memory_hotplug.c
> +++ b/mm/memory_hotplug.c
> @@ -201,7 +201,7 @@ static void grow_zone_span(struct zone *zone, unsigned long start_pfn,
>   	zone_span_writelock(zone);
>
>   	old_zone_end_pfn = zone->zone_start_pfn + zone->spanned_pages;
> -	if (start_pfn < zone->zone_start_pfn)
> +	if (!zone->zone_start_pfn || start_pfn < zone->zone_start_pfn)
>   		zone->zone_start_pfn = start_pfn;
>
>   	zone->spanned_pages = max(old_zone_end_pfn, end_pfn) -
> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> index 009ac28..637b4f8 100644
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -3991,8 +3991,6 @@ int __meminit init_currently_empty_zone(struct zone *zone,
>   		return ret;
>   	pgdat->nr_zones = zone_idx(zone) + 1;
>
> -	zone->zone_start_pfn = zone_start_pfn;
> -
>   	mminit_dprintk(MMINIT_TRACE, "memmap_init",
>   			"Initialising map node %d zone %lu pfns %lu -> %lu\n",
>   			pgdat->node_id,
> @@ -4459,6 +4457,7 @@ static void __paginginit free_area_init_core(struct pglist_data *pgdat,
>   		ret = init_currently_empty_zone(zone, zone_start_pfn,
>   						size, MEMMAP_EARLY);
>   		BUG_ON(ret);
> +		zone->zone_start_pfn = zone_start_pfn;
>   		memmap_init(size, nid, j, zone_start_pfn);
>   		zone_start_pfn += size;
>   	}
>



  reply	other threads:[~2012-09-11 10:19 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-10  8:58 [V4 PATCH 00/26] memory,numa: introduce MOVABLE-dedicated node and online_movable for hotplug Lai Jiangshan
2012-09-10  8:58 ` [V4 PATCH 01/26] page_alloc.c: don't subtract unrelated memmap from zone's present pages Lai Jiangshan
2012-09-10  8:58 ` [V4 PATCH 02/26] memory_hotplug: fix missing nodemask management Lai Jiangshan
2012-09-11  2:55   ` Wen Congyang
2012-09-10  8:58 ` [V4 PATCH 03/26] slub, hotplug: ignore unrelated node's hot-adding and hot-removing Lai Jiangshan
2012-09-10  8:58 ` [V4 PATCH 04/26] node: cleanup node_state_attr Lai Jiangshan
2012-09-10  8:58 ` [V4 PATCH 05/26] node_states: introduce N_MEMORY Lai Jiangshan
2012-09-10  8:58 ` [V4 PATCH 06/26] cpuset: use N_MEMORY instead N_HIGH_MEMORY Lai Jiangshan
2012-09-10  8:58 ` [V4 PATCH 07/26] procfs: " Lai Jiangshan
2012-09-10  8:59 ` [V4 PATCH 08/26] memcontrol: " Lai Jiangshan
2012-09-10  8:59 ` [V4 PATCH 09/26] oom: " Lai Jiangshan
2012-09-10  8:59 ` [V4 PATCH 10/26] mm,migrate: " Lai Jiangshan
2012-09-10  8:59 ` [V4 PATCH 11/26] mempolicy: " Lai Jiangshan
2012-09-10  8:59 ` [V4 PATCH 12/26] hugetlb: " Lai Jiangshan
2012-09-10  8:59 ` [V4 PATCH 13/26] vmstat: " Lai Jiangshan
2012-09-10  8:59 ` [V4 PATCH 14/26] kthread: " Lai Jiangshan
2012-09-10  8:59 ` [V4 PATCH 15/26] init: " Lai Jiangshan
2012-09-10  8:59 ` [V4 PATCH 16/26] vmscan: " Lai Jiangshan
2012-09-10  8:59 ` [V4 PATCH 17/26] page_alloc: use N_MEMORY instead N_HIGH_MEMORY change the node_states initialization Lai Jiangshan
2012-09-10  8:59 ` [V4 PATCH 18/26] hotplug: update nodemasks management Lai Jiangshan
2012-09-10  8:59 ` [V4 PATCH 19/26] numa: add CONFIG_MOVABLE_NODE for movable-dedicated node Lai Jiangshan
2012-09-10  8:59 ` [V4 PATCH 20/26] page_alloc: add kernelcore_max_addr Lai Jiangshan
2012-09-10  8:59 ` [V4 PATCH 21/26] x86: get pg_data_t's memory from other node Lai Jiangshan
2012-09-10  8:59 ` [V4 PATCH 22/26] x86: use memblock_set_current_limit() to set memblock.current_limit Lai Jiangshan
2012-09-10  8:59 ` [V4 PATCH 23/26] memblock: limit memory address from memblock Lai Jiangshan
2012-09-10  8:59 ` [V4 PATCH 24/26] memblock: compare current_limit with end variable at memblock_find_in_range_node() Lai Jiangshan
2012-09-10  8:59 ` [V4 PATCH 25/26] mm, memory-hotplug: add online_movable and online_kernel Lai Jiangshan
2012-09-10  8:59 ` [V4 PATCH 26/26] memory_hotplug: handle empty zone when online_movable/online_kernel Lai Jiangshan
2012-09-11  0:40 ` [V4 PATCH 00/26] memory,numa: introduce MOVABLE-dedicated node and online_movable for hotplug Yasuaki Ishimatsu
2012-09-11  1:22   ` Lai Jiangshan
2012-09-11  1:37     ` Yasuaki Ishimatsu
2012-09-11  3:09       ` Lai Jiangshan
2012-09-11  9:44   ` [V4 PATCH 27/27] memory,hotplug: Don't modify the zone_start_pfn outside of zone_span_writelock() Lai Jiangshan
2012-09-11 10:18     ` Yasuaki Ishimatsu [this message]
2012-09-12  1:38       ` Lai Jiangshan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=504F0FE6.5090709@jp.fujitsu.com \
    --to=isimatu.yasuaki@jp.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=jiang.liu@huawei.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=rientjes@google.com \
    --cc=rusty@rustcorp.com.au \
    --cc=wency@cn.fujitsu.com \
    --cc=x86@kernel.org \
    --cc=yinghai@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox