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
