linux-kernel - Re: [PATCH] mm/page_alloc: Deprecate kernelcore=nn and movable

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]

Message-ID: <20180717233100.GH1724@MiWiFi-R3L-srv>
Date:   Wed, 18 Jul 2018 07:31:00 +0800
From:   Baoquan He <bhe@...hat.com>
To:     David Rientjes <rientjes@...gle.com>
Cc:     mhocko@...nel.org, linux-kernel@...r.kernel.org,
        linux-mm@...ck.org, akpm@...ux-foundation.org, corbet@....net,
        linux-doc@...r.kernel.org
Subject: Re: [PATCH] mm/page_alloc: Deprecate kernelcore=nn and movable_core=

On 07/17/18 at 01:46pm, David Rientjes wrote:
> On Tue, 17 Jul 2018, Baoquan He wrote:
> 
> > We can still use 'kernelcore=mirror' or 'movable_node' for the usage
> > of hotplug and movable zone. If somebody shows up with a valid usecase
> > we can reconsider.
> > 
> 
> We actively use kernelcore=n%, I had recently added support for the option 
> in the first place in 4.17.  It's certainly not deprecated.

Thanks for telling. Just for curiosity, could you tell the scenario you
are using kernelcore=n%? Since it evenly spread movable area on nodes,
we may not be able to physically hot unplug/plug RAM.

Thanks
Baoquan