linux-kernel - RE: [PATCH v5 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: <3908561D78D1C84285E8C5FCA982C28F1C986D98@ORSMSX108.amr.corp.intel.com>
Date:	Thu, 17 Jan 2013 16:30:31 +0000
From:	"Luck, Tony" <tony.luck@...el.com>
To:	"H. Peter Anvin" <hpa@...or.com>,
	Yasuaki Ishimatsu <isimatu.yasuaki@...fujitsu.com>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	Tang Chen <tangchen@...fujitsu.com>,
	"jiang.liu@...wei.com" <jiang.liu@...wei.com>,
	"wujianguo@...wei.com" <wujianguo@...wei.com>,
	"wency@...fujitsu.com" <wency@...fujitsu.com>,
	"laijs@...fujitsu.com" <laijs@...fujitsu.com>,
	"linfeng@...fujitsu.com" <linfeng@...fujitsu.com>,
	"yinghai@...nel.org" <yinghai@...nel.org>,
	"rob@...dley.net" <rob@...dley.net>,
	"kosaki.motohiro@...fujitsu.com" <kosaki.motohiro@...fujitsu.com>,
	"minchan.kim@...il.com" <minchan.kim@...il.com>,
	"mgorman@...e.de" <mgorman@...e.de>,
	"rientjes@...gle.com" <rientjes@...gle.com>,
	"guz.fnst@...fujitsu.com" <guz.fnst@...fujitsu.com>,
	"rusty@...tcorp.com.au" <rusty@...tcorp.com.au>,
	"lliubbo@...il.com" <lliubbo@...il.com>,
	"jaegeuk.hanse@...il.com" <jaegeuk.hanse@...il.com>,
	"glommer@...allels.com" <glommer@...allels.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-mm@...ck.org" <linux-mm@...ck.org>
Subject: RE: [PATCH v5 0/5] Add movablecore_map boot option

> 2. If the user *does* care which nodes are movable, then the user needs 
> to be able to specify that *in a way that makes sense to the user*. 
> This may mean involving the DMI information as well as SRAT in order to 
> get "silk screen" type information out.

One reason they might care would be which I/O devices are connected
to each node.  DMI might be a good way to get an invariant name for the
node, but they might also want to specify in terms of what they actually
want. E.g. "eth0 and eth4 are a redundant bonded pair of NICs - don't
mark both these nodes as removable".  Though this is almost certainly not
a job for kernel options, but for some user configuration tool that would
spit out the DMI names.

-Tony