[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <50B598E7.6090506@huawei.com>
Date: Wed, 28 Nov 2012 12:53:59 +0800
From: Jianguo Wu <wujianguo@...wei.com>
To: Tang Chen <tangchen@...fujitsu.com>
CC: wujianguo <wujianguo106@...il.com>, <hpa@...or.com>,
<akpm@...ux-foundation.org>, <rob@...dley.net>,
<isimatu.yasuaki@...fujitsu.com>, <laijs@...fujitsu.com>,
<wency@...fujitsu.com>, <linfeng@...fujitsu.com>,
<jiang.liu@...wei.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>
Subject: Re: [PATCH v2 0/5] Add movablecore_map boot option
On 2012/11/28 11:47, Tang Chen wrote:
> On 11/27/2012 11:10 AM, wujianguo wrote:
>>
>> Hi Tang,
>> DMA address can't be set as movable, if some one boot kernel with
>> movablecore_map=4G@...00000 or other memory region that contains DMA address,
>> system maybe boot failed. Should this case be handled or mentioned
>> in the change log and kernel-parameters.txt?
>
> Hi Wu,
>
> I think we can use MAX_DMA_PFN and MAX_DMA32_PFN to prevent setting DMA
> address as movable. Just ignore the address lower than them, and set
> the rest as movable. How do you think ?
>
I think it's OK for now.
> And, since we cannot figure out the minimum of memory kernel needs, I
> think for now, we can just add some warning into kernel-parameters.txt.
>
> Thanks. :)
>
>>
>> Thanks,
>> Jianguo Wu
>>
>
> .
>
--
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