[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <50B6B936.10200@cn.fujitsu.com>
Date: Thu, 29 Nov 2012 09:24:06 +0800
From: Tang Chen <tangchen@...fujitsu.com>
To: Jaegeuk Hanse <jaegeuk.hanse@...il.com>
CC: Wen Congyang <wency@...fujitsu.com>,
Jiang Liu <jiang.liu@...wei.com>, Bob Liu <lliubbo@...il.com>,
hpa@...or.com, akpm@...ux-foundation.org, rob@...dley.net,
isimatu.yasuaki@...fujitsu.com, laijs@...fujitsu.com,
linfeng@...fujitsu.com, yinghai@...nel.org,
kosaki.motohiro@...fujitsu.com, minchan.kim@...il.com,
mgorman@...e.de, rientjes@...gle.com, rusty@...tcorp.com.au,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
linux-doc@...r.kernel.org, m.szyprowski@...sung.com
Subject: Re: [PATCH v2 0/5] Add movablecore_map boot option
On 11/29/2012 08:43 AM, Jaegeuk Hanse wrote:
> Hi Tang,
>
> I haven't read the patchset yet, but could you give a short describe how
> you design your implementation in this patchset?
>
> Regards,
> Jaegeuk
>
Hi Jaegeuk,
Thanks for your joining in. :)
This feature is used in memory hotplug.
In order to implement a whole node hotplug, we need to make sure the
node contains no kernel memory, because memory used by kernel could
not be migrated. (Since the kernel memory is directly mapped,
VA = PA + __PAGE_OFFSET. So the physical address could not be changed.)
With this boot option, user could specify all the memory on a node to
be movable(which means they are in ZONE_MOVABLE), so that the node
could be hot-removed.
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists