linux-kernel - Re: [PATCH 2/2] arm64: mm: support bootparam max

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: <YbtK42WAk3aL/Zqr@kernel.org>
Date:   Thu, 16 Dec 2021 16:19:15 +0200
From:   Mike Rapoport <rppt@...nel.org>
To:     Peng Fan <peng.fan@....com>
Cc:     Jan Kiszka <jan.kiszka@...mens.com>,
        Ard Biesheuvel <ardb@...nel.org>,
        "Peng Fan (OSS)" <peng.fan@....nxp.com>,
        Catalin Marinas <catalin.marinas@....com>,
        Will Deacon <will@...nel.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        David Hildenbrand <david@...hat.com>,
        Anshuman Khandual <anshuman.khandual@....com>,
        Geert Uytterhoeven <geert+renesas@...der.be>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        dl-linux-imx <linux-imx@....com>
Subject: Re: [PATCH 2/2] arm64: mm: support bootparam max_addr

On Wed, Dec 15, 2021 at 12:05:36PM +0000, Peng Fan wrote:
> > Subject: Re: [PATCH 2/2] arm64: mm: support bootparam max_addr
> > 
> > > > > > > If pass "mem=1024MB", the actually max addr will be
> > > > > > > 0x81000000.  However if need the max addr be 0x80000000,
> > > > > > > mem=1008MB should be used.
> > > > > > >
> 
> BTW, do you think max_addr would be an option be added to memblock
> common code mm/memblock.c?

You have a working solution with mem=1008MB, I don't see a need for
additional kernel parameter.

-- 
Sincerely yours,
Mike.