linux-kernel - Re: [PATCH v2 0/5] Add movablecore

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <50B48F0B.60704@jp.fujitsu.com>
Date:	Tue, 27 Nov 2012 18:59:39 +0900
From:	Yasuaki Ishimatsu <isimatu.yasuaki@...fujitsu.com>
To:	"H. Peter Anvin" <hpa@...or.com>,
	Tang Chen <tangchen@...fujitsu.com>
CC:	Bob Liu <lliubbo@...il.com>, <akpm@...ux-foundation.org>,
	<rob@...dley.net>, <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

Hi HPA and Tang,

2012/11/27 17:49, H. Peter Anvin wrote:
> On 11/27/2012 12:29 AM, Tang Chen wrote:
>> Another approach is like the following:
>> movable_node = 1,3-5,8
>> This could set all the memory on the nodes to be movable. And the rest
>> of memory works as usual. But movablecore_map is more flexible.
>
> ... but *much* harder for users, so movable_node is better in most cases.

It seems that movable_node is easier to use than movablecore_map.
But I do not think movable_node is better because the node number is set
by OS and changed easily.


For exmaple:
If system has 4 nodes and we set moveble_node=2, we can hot remove node2.

    node0   node1   node2   node3
   +-----+ +-----+ +-----+ +-----+
   |     | |     | |/////| |     |
   |     | |     | |/////| |     |
   |     | |     | |/////| |     |
   |     | |     | |/////| |     |
   +-----+ +-----+ +-----+ +-----+
                   movable
                    node

But if we hot remove node2 and reboot the system, node3 is changed to node2
and set to movable node.

    node0   node1           node2
   +-----+ +-----+         +-----+
   |     | |     |         |/////|
   |     | |     |         |/////|
   |     | |     |         |/////|
   |     | |     |         |/////|
   +-----+ +-----+         +-----+
                           movable
                            node

Originally, node3 is not movable node. Changing the node attribution to
movable node is not intended. So if user uses movable_node,
user must confirm whether boot option is correctly set at hotplug.

But memory range is set by firmware and not changed. So if we set node2
as movable node by movablecore_map, the issue does not occur.

Thanks,
Yasuaki Ishimatsu

>
> 	-hpa
>


--
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/