Re: [PATCH RFCv2 3/4] mm/memory_hotplug: Introduce and use more memory types
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: David Hildenbrand <david@xxxxxxxxxx>
- Subject: Re: [PATCH RFCv2 3/4] mm/memory_hotplug: Introduce and use more memory types
- From: Michal Suchánek <msuchanek@xxxxxxx>
- Date: Tue, 4 Dec 2018 10:44:54 +0100
- Cc: linux-mm@xxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, linux-ia64@xxxxxxxxxxxxxxx, linuxppc-dev@xxxxxxxxxxxxxxxx, linux-s390@xxxxxxxxxxxxxxx, linux-sh@xxxxxxxxxxxxxxx, linux-acpi@xxxxxxxxxxxxxxx, devel@xxxxxxxxxxxxxxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxxx, x86@xxxxxxxxxx, Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>, Paul Mackerras <paulus@xxxxxxxxx>, Michael Ellerman <mpe@xxxxxxxxxxxxxx>, "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>, Len Brown <lenb@xxxxxxxxxx>, Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>, "K. Y. Srinivasan" <kys@xxxxxxxxxxxxx>, Haiyang Zhang <haiyangz@xxxxxxxxxxxxx>, Stephen Hemminger <sthemmin@xxxxxxxxxxxxx>, Martin Schwidefsky <schwidefsky@xxxxxxxxxx>, Heiko Carstens <heiko.carstens@xxxxxxxxxx>, Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx>, Juergen Gross <jgross@xxxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>, Rashmica Gupta <rashmica.g@xxxxxxxxx>, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, Pavel Tatashin <pavel.tatashin@xxxxxxxxxxxxx>, Balbir Singh <bsingharora@xxxxxxxxx>, Michael Neuling <mikey@xxxxxxxxxxx>, Nathan Fontenot <nfont@xxxxxxxxxxxxxxxxxx>, YueHaibing <yuehaibing@xxxxxxxxxx>, Vasily Gorbik <gor@xxxxxxxxxxxxx>, Ingo Molnar <mingo@xxxxxxxxxx>, Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>, "mike.travis@xxxxxxx" <mike.travis@xxxxxxx>, Oscar Salvador <osalvador@xxxxxxx>, Joonsoo Kim <iamjoonsoo.kim@xxxxxxx>, Mathieu Malaterre <malat@xxxxxxxxxx>, Michal Hocko <mhocko@xxxxxxxx>, Arun KS <arunks@xxxxxxxxxxxxxx>, Andrew Banman <andrew.banman@xxxxxxx>, Dave Hansen <dave.hansen@xxxxxxxxxxxxxxx>, Vitaly Kuznetsov <vkuznets@xxxxxxxxxx>, Dan Williams <dan.j.williams@xxxxxxxxx>
- In-reply-to: <20181130175922.10425-4-david@redhat.com>
- References: <20181130175922.10425-1-david@redhat.com> <20181130175922.10425-4-david@redhat.com>
On Fri, 30 Nov 2018 18:59:21 +0100
David Hildenbrand <david@xxxxxxxxxx> wrote:
> Let's introduce new types for different kinds of memory blocks and use
> them in existing code. As I don't see an easy way to split this up,
> do it in one hunk for now.
>
> acpi:
> Use DIMM or DIMM_UNREMOVABLE depending on hotremove support in the kernel.
> Properly change the type when trying to add memory that was already
> detected and used during boot (so this memory will correctly end up as
> "acpi" in user space).
>
> pseries:
> Use DIMM or DIMM_UNREMOVABLE depending on hotremove support in the kernel.
> As far as I see, handling like in the acpi case for existing blocks is
> not required.
>
> probed memory from user space:
> Use DIMM_UNREMOVABLE as there is no interface to get rid of this code
> again.
>
> hv_balloon,xen/balloon:
> Use BALLOON. As simple as that :)
>
> s390x/sclp:
> Use a dedicated type S390X_STANDBY as this type of memory and it's
> semantics are very s390x specific.
>
> powernv/memtrace:
> Only allow to use BOOT memory for memtrace. I consider this code in
> general dangerous, but we have to keep it working ... most probably just
> a debug feature.
I don't think it should be arbitrarily restricted like that.
Thanks
Michal
[Index of Archives]
[Linux Kernel]
[Sparc Linux]
[DCCP]
[Linux ARM]
[Yosemite News]
[Linux SCSI]
[Linux x86_64]
[Linux for Ham Radio]