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: Mon, 14 Nov 2016 13:34:52 -0600 From: Reza Arbab <arbab@...ux.vnet.ibm.com> To: Michael Ellerman <mpe@...erman.id.au> Cc: Benjamin Herrenschmidt <benh@...nel.crashing.org>, Paul Mackerras <paulus@...ba.org>, Andrew Morton <akpm@...ux-foundation.org>, Rob Herring <robh+dt@...nel.org>, Frank Rowand <frowand.list@...il.com>, Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>, "H. Peter Anvin" <hpa@...or.com>, linuxppc-dev@...ts.ozlabs.org, linux-mm@...ck.org, devicetree@...r.kernel.org, Bharata B Rao <bharata@...ux.vnet.ibm.com>, Nathan Fontenot <nfont@...ux.vnet.ibm.com>, Stewart Smith <stewart@...ux.vnet.ibm.com>, Alistair Popple <apopple@....ibm.com>, Balbir Singh <bsingharora@...il.com>, "Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>, linux-kernel@...r.kernel.org Subject: Re: [PATCH v6 4/4] of/fdt: mark hotpluggable memory On Mon, Nov 14, 2016 at 10:59:43PM +1100, Michael Ellerman wrote: >So I'm not opposed to this, but it is a little vague. > >What does the "hotpluggable" property really mean? > >Is it just a hint to the operating system? (which may or may not be >Linux). > >Or is it a direction, "this memory must be able to be hotunplugged"? > >I think you're intending the former, ie. a hint, which is probably OK. >But it needs to be documented clearly. Yes, you've got it right. It's just a hint, not a mandate. I'm about to send v7 which adds a description of "hotpluggable" in the documentation. Hopefully I've explained it well enough there. -- Reza Arbab
Powered by blists - more mailing lists