[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <50F440F5.3030006@zytor.com>
Date: Mon, 14 Jan 2013 09:31:33 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: Tang Chen <tangchen@...fujitsu.com>
CC: akpm@...ux-foundation.org, jiang.liu@...wei.com,
wujianguo@...wei.com, wency@...fujitsu.com, laijs@...fujitsu.com,
linfeng@...fujitsu.com, yinghai@...nel.org,
isimatu.yasuaki@...fujitsu.com, rob@...dley.net,
kosaki.motohiro@...fujitsu.com, minchan.kim@...il.com,
mgorman@...e.de, rientjes@...gle.com, guz.fnst@...fujitsu.com,
rusty@...tcorp.com.au, lliubbo@...il.com, jaegeuk.hanse@...il.com,
tony.luck@...el.com, glommer@...allels.com,
linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH v5 0/5] Add movablecore_map boot option
On 01/14/2013 01:15 AM, Tang Chen wrote:
>
> For now, users can disable this functionality by not specifying the boot option.
> Later, we will post SRAT support, and add another option value "movablecore_map=acpi"
> to using SRAT.
>
I still think the option "movablecore_map" is uglier than hell. "core"
could just as easily refer to CPU cores there, but it is a memory mem.
"movablemem" seems more appropriate.
Again, without SRAT I consider this patchset to be largely useless for
anything other than prototyping work.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
--
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