linux-kernel - Re: [PATCH v6 4/4] of/fdt: mark hotpluggable memory

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] [day] [month] [year] [list]

Message-ID: <5861B11E.1050303@gmail.com>
Date:   Mon, 26 Dec 2016 16:09:02 -0800
From:   Frank Rowand <frowand.list@...il.com>
To:     Heinrich Schuchardt <xypron.glpk@....de>,
        Reza Arbab <arbab@...ux.vnet.ibm.com>
Cc:     Balbir Singh <bsingharora@...il.com>,
        "Aneesh Kumar K . V" <aneesh.kumar@...ux.vnet.ibm.com>,
        "H . Peter Anvin" <hpa@...or.com>,
        Alistair Popple <apopple@....ibm.com>,
        Benjamin Herrenschmidt <benh@...nel.crashing.org>,
        Bharata B Rao <bharata@...ux.vnet.ibm.com>,
        Ingo Molnar <mingo@...hat.com>,
        Michael Ellerman <mpe@...erman.id.au>,
        Nathan Fontenot <nfont@...ux.vnet.ibm.com>,
        Paul Mackerras <paulus@...ba.org>,
        Rob Herring <robh+dt@...nel.org>,
        Stewart Smith <stewart@...ux.vnet.ibm.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        Andrew Morton <akpm@...ux-foundation.org>,
        devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-mm@...ck.org
Subject: Re: [PATCH v6 4/4] of/fdt: mark hotpluggable memory

On 12/25/16 01:02, Heinrich Schuchardt wrote:
> The patch adds a new property "linux,hotpluggable" to memory nodes of the
> device tree.
> 
> memory@0 {
> 	reg = <0x0 0x01000000 0x0 0x7f000000>;
> 	linux,hotpluggable;
> }
> 
> Memory areas marked by this property can later be disabled using the hotplugging
> API. Especially for virtual machines this is a very useful capability.
> 
> Unfortunately the notation chosen does not fit well with the concept of
> devicetree overlays which allow to change the devicetree during runtime.

Why would one want to change the hot pluggable memory node via an overlay?
In other words, what is missing from the hot pluggable memory paradigm
that instead requires overlays?

If something is missing from the hot pluggable memory code, then it seems
to me that it should be added to that code instead of hacking around it
by using device tree overlays.

-Frank

> 
> I suggest to use the following notation
> 
> memory@0 {
> 	compatible = "linux,hotpluggable-memory";
> 	reg = <0x0 0x01000000 0x0 0x7f000000>;
> 	status = "disabled";
> }
> 
> This will allow us to write a device driver that can react to changes of the
> devicetree made via devicetree overlays.
> 
> This driver could react to the change of the status between "okay" and
> "disabled" and update the memory status accordingly.
> 
> Further we could use devicetree overlays to provide additional hotpluggable
> memory.
> 
> The referenced patch has already been pulled for 4.10. But I hope it is not
> too late for this design change.
> 
> Best regards
> 
> Heinrich Schuchardt
>