lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 28 Nov 2012 13:17:08 +0800 From: Jiang Liu <jiang.liu@...wei.com> To: Wen Congyang <wency@...fujitsu.com> CC: Tang Chen <tangchen@...fujitsu.com>, wujianguo <wujianguo106@...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> Subject: Re: [PATCH v2 0/5] Add movablecore_map boot option On 2012-11-28 13:21, Wen Congyang wrote: > At 11/28/2012 12:01 PM, Jiang Liu Wrote: >> 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 ? >>> >>> 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. :) >> On one other OS, there is a mechanism to dynamically convert pages from >> movable zones into normal zones. > > The OS auto does it? Or the user coverts it? > > We can convert pages from movable zones into normal zones by the following > interface: > echo online_kernel >/sys/devices/system/memory/memoryX/state > > We have posted a patchset to implement it, and it is in mm tree now. OS automatically converts it, no manual operations needed. -- 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