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: Tue, 15 Jan 2013 10:23:20 +0900 From: Yasuaki Ishimatsu <isimatu.yasuaki@...fujitsu.com> To: "Luck, Tony" <tony.luck@...el.com> CC: Andrew Morton <akpm@...ux-foundation.org>, "H. Peter Anvin" <hpa@...or.com>, 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 2013/01/15 7:41, Luck, Tony wrote: >> hm, why. Obviously SRAT support will improve things, but is it >> actually unusable/unuseful with the command line configuration? > > Users will want to set these moveable zones along node boundaries > (the whole purpose is to be able to remove a node by making sure > the kernel won't allocate anything tricky in it, right?) Yes > So raw addresses > are usable ... but to get them right the user will have to go parse the > SRAT table manually to come up with the addresses. I don't think so because user can easily get raw address by kernel message in x86. Here are kernel messages of x86 architecture. --- [ 0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff] [ 0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x7ffffffff] [ 0.000000] SRAT: Node 1 PXM 2 [mem 0x1000000000-0x17ffffffff] [ 0.000000] SRAT: Node 2 PXM 3 [mem 0x1800000000-0x1fffffffff] [ 0.000000] SRAT: Node 3 PXM 4 [mem 0x2000000000-0x27ffffffff] [ 0.000000] SRAT: Node 4 PXM 5 [mem 0x2800000000-0x2fffffffff] [ 0.000000] SRAT: Node 5 PXM 6 [mem 0x3000000000-0x37ffffffff] [ 0.000000] SRAT: Node 6 PXM 7 [mem 0x3800000000-0x3fffffffff] [ 0.000000] SRAT: Node 7 PXM 1 [mem 0x800000000-0xfffffffff] --- Thanks, Yasuaki Ishimatsu > Any time you > make the user go off and do some tedious calculation that the computer > should have done for them is user-abuse. > > -Tony > -- 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