linux-kernel - Re: [PATCH 2/2] arm64: add support for 43bit physical address

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: <20180705183452.vaaxjsrus6lnqyzt@armageddon.cambridge.arm.com>
Date:   Thu, 5 Jul 2018 19:34:53 +0100
From:   Catalin Marinas <catalin.marinas@....com>
To:     "Nikunj Kela (nkela)" <nkela@...co.com>
Cc:     "xe-kernel@...ernal.cisco.com" <xe-kernel@...ernal.cisco.com>,
        Will Deacon <will.deacon@....com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH 2/2] arm64: add support for 43bit physical address

On Tue, Jul 03, 2018 at 06:35:32PM +0000, Nikunj Kela (nkela) wrote:
> We are trying to reduce the memory allocation needed for kdump kernel.
> We want to reserve less than 32M for kdump kernel if possible. We are
> able to get ~14M saving by the proposed change.

Have you tried disabling SPARSEMEM and using FLATMEM for this case? With
32M you wouldn't need more than a section anyway. It needs some tweaking
of the arm64 Kconfig and probably fail to build.

-- 
Catalin