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]

Date:	Thu, 17 Jan 2013 22:25:20 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Yasuaki Ishimatsu <isimatu.yasuaki@...fujitsu.com>,
	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
	tony.luck@...el.com
CC:	akpm@...ux-foundation.org, tangchen@...fujitsu.com,
	jiang.liu@...wei.com, wujianguo@...wei.com, wency@...fujitsu.com,
	laijs@...fujitsu.com, linfeng@...fujitsu.com, yinghai@...nel.org,
	rob@...dley.net, 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,
	glommer@...allels.com, linux-kernel@...r.kernel.org,
	linux-mm@...ck.org
Subject: Re: [PATCH v5 0/5] Add movablecore_map boot option

We already do DMI parsing in the kernel...

Yasuaki Ishimatsu <isimatu.yasuaki@...fujitsu.com> wrote:

>2013/01/18 5:28, KOSAKI Motohiro wrote:
>> On 1/17/2013 11:30 AM, Luck, Tony wrote:
>>>> 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.
>>
>> I agree DMI parsing should be done in userland if we really need DMI
>parsing.
>>
>
>If users use the boot parameter for bugs or debugging,  users need
>a method which sets in detail range of movable memory. So specifying
>node number is not enough because whole memory becomes movable memory.
>
>For this, we are discussing other ways, memory range and DMI
>information.
>By using DMI information, users may get an invariant name. But is it
>really user friendly interface? I don't think so.
>
>You will think using memory range is not user friendly interface too.
>But I think that using memory range is friendlier than using DMI
>information since we can get easily memory range. So from developper
>side, using memory range is good.
>
>Of course, using SRAT information is necessary solution. So we are
>developing it now.
>
>Thanks,
>Yasuaki Ishimatsu

-- 
Sent from my mobile phone. Please excuse brevity and lack of formatting.
--
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/