linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@suse.com>
To: Wei Yang <richard.weiyang@gmail.com>
Cc: linux-mm@kvack.org, akpm@linux-foundation.org,
	mgorman@techsingularity.net, osalvador@suse.de
Subject: Re: [PATCH] mm, page_alloc: clear zone_movable_pfn if the node doesn't have ZONE_MOVABLE
Date: Mon, 17 Dec 2018 11:25:34 +0100	[thread overview]
Message-ID: <20181217102534.GF30879@dhcp22.suse.cz> (raw)
In-Reply-To: <20181216125624.3416-1-richard.weiyang@gmail.com>

On Sun 16-12-18 20:56:24, Wei Yang wrote:
> A non-zero zone_movable_pfn indicates this node has ZONE_MOVABLE, while
> current implementation doesn't comply with this rule when kernel
> parameter "kernelcore=" is used.
> 
> Current implementation doesn't harm the system, since the value in
> zone_movable_pfn is out of the range of current zone. While user would
> see this message during bootup, even that node doesn't has ZONE_MOVABLE.
> 
>     Movable zone start for each node
>       Node 0: 0x0000000080000000

I am sorry but the above description confuses me more than it helps.
Could you start over again and describe the user visible problem, then
follow up with the udnerlying bug and finally continue with a proposed
fix?
-- 
Michal Hocko
SUSE Labs

  reply	other threads:[~2018-12-17 10:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-16 12:56 Wei Yang
2018-12-17 10:25 ` Michal Hocko [this message]
2018-12-17 14:18   ` Wei Yang
2018-12-18 12:14     ` Michal Hocko
2018-12-18 14:39       ` Wei Yang
2018-12-18 14:47         ` Michal Hocko
2018-12-18 20:27           ` Wei Yang
2018-12-19  6:56             ` Michal Hocko
2018-12-19 12:56               ` Wei Yang

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=20181217102534.GF30879@dhcp22.suse.cz \
    --to=mhocko@suse.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@techsingularity.net \
    --cc=osalvador@suse.de \
    --cc=richard.weiyang@gmail.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