From: Yasuaki Ishimatsu <yasu.isimatu@gmail.com>
To: Xishi Qiu <qiuxishi@huawei.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>,
Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
izumi.taku@jp.fujitsu.com, Tang Chen <tangchen@cn.fujitsu.com>,
Gu Zheng <guz.fnst@cn.fujitsu.com>,
Xiexiuqi <xiexiuqi@huawei.com>, Mel Gorman <mgorman@suse.de>,
David Rientjes <rientjes@google.com>,
Linux MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2 V2] memory-hotplug: fix BUG_ON in move_freepages()
Date: Sun, 19 Apr 2015 18:56:17 -0700 (PDT) [thread overview]
Message-ID: <55345cc1.0fc98c0a.1318.54fb@mx.google.com> (raw)
In-Reply-To: <55345756.40902@huawei.com>
When hot adding memory and creating new node, the node is offline.
And after calling node_set_online(), the node becomes online.
Oh, sorry. I misread your ptaches.
Thanks,
Yasuaki Ishimatsu
On Mon, 20 Apr 2015 09:33:10 +0800
Xishi Qiu <qiuxishi@huawei.com> wrote:
> On 2015/4/18 4:05, Yasuaki Ishimatsu wrote:
>
> >
> > Your patches will fix your issue.
> > But, if BIOS reports memory first at node hot add, pgdat can
> > not be initialized.
> >
> > Memory hot add flows are as follows:
> >
> > add_memory
> > ...
> > -> hotadd_new_pgdat()
> > ...
> > -> node_set_online(nid)
> >
> > When calling hotadd_new_pgdat() for a hot added node, the node is
> > offline because node_set_online() is not called yet. So if applying
> > your patches, the pgdat is not initialized in this case.
> >
> > Thanks,
> > Yasuaki Ishimatsu
> >
>
> Hi Yasuaki,
>
> I'm not quite understand, when BIOS reports memory first, why pgdat
> can not be initialized?
> When hotadd a new node, hotadd_new_pgdat() will be called too, and
> when hotadd memory to a existent node, it's no need to call hotadd_new_pgdat(),
> right?
>
> Thanks,
> Xishi Qiu
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-04-20 1:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 10:50 [PATCH 1/2 V2] memory-hotplug: fix BUG_ON in move_freepages() Xishi Qiu
2015-04-17 20:05 ` Yasuaki Ishimatsu
2015-04-20 1:33 ` Xishi Qiu
2015-04-20 1:56 ` Yasuaki Ishimatsu [this message]
2015-04-20 2:11 ` Yasuaki Ishimatsu
2015-04-20 2:08 ` Gu Zheng
2015-04-20 2:09 ` Gu Zheng
2015-04-20 2:59 ` Xishi Qiu
2015-04-20 3:15 ` Yasuaki Ishimatsu
2015-04-20 3:34 ` Xishi Qiu
2015-04-20 2:23 ` Yasuaki Ishimatsu
2015-04-20 1:42 ` Gu Zheng
2015-04-20 2:45 ` Xishi Qiu
2015-04-20 3:29 ` Yasuaki Ishimatsu
2015-04-20 3:42 ` Xishi Qiu
2015-04-20 18:23 ` Yasuaki Ishimatsu
2015-04-21 1:31 ` Xishi Qiu
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=55345cc1.0fc98c0a.1318.54fb@mx.google.com \
--to=yasu.isimatu@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=guz.fnst@cn.fujitsu.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=izumi.taku@jp.fujitsu.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=qiuxishi@huawei.com \
--cc=rientjes@google.com \
--cc=tangchen@cn.fujitsu.com \
--cc=xiexiuqi@huawei.com \
/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;
as well as URLs for NNTP newsgroup(s).