linux-kernel - Re: [PATCH -next v4 1/2] riscv: kdump: Implement crashkernel=X,[high,low]

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: <ZDUN2+WG3OKGN/oq@kernel.org>
Date:   Tue, 11 Apr 2023 09:35:55 +0200
From:   Simon Horman <horms@...nel.org>
To:     Chen Jiahao <chenjiahao16@...wei.com>
Cc:     linux-kernel@...r.kernel.org, linux-riscv@...ts.infradead.org,
        kexec@...ts.infradead.org, linux-doc@...r.kernel.org,
        paul.walmsley@...ive.com, palmer@...belt.com,
        conor.dooley@...rochip.com, guoren@...nel.org, heiko@...ech.de,
        bjorn@...osinc.com, alex@...ti.fr, akpm@...ux-foundation.org,
        atishp@...osinc.com, bhe@...hat.com, thunder.leizhen@...wei.com
Subject: Re: [PATCH -next v4 1/2] riscv: kdump: Implement
 crashkernel=X,[high,low]

On Mon, Apr 10, 2023 at 09:05:52PM +0800, Chen Jiahao wrote:
> On riscv, the current crash kernel allocation logic is trying to
> allocate within 32bit addressible memory region by default, if
> failed, try to allocate without 4G restriction.
> 
> In need of saving DMA zone memory while allocating a relatively large
> crash kernel region, allocating the reserved memory top down in
> high memory, without overlapping the DMA zone, is a mature solution.
> Here introduce the parameter option crashkernel=X,[high,low].
> 
> One can reserve the crash kernel from high memory above DMA zone range
> by explicitly passing "crashkernel=X,high"; or reserve a memory range
> below 4G with "crashkernel=X,low".
> 
> Signed-off-by: Chen Jiahao <chenjiahao16@...wei.com>
> Acked-by: Guo Ren <guoren@...nel.org>
> Reviewed-by: Zhen Lei <thunder.leizhen@...wei.com>

Reviewed-by: Simon Horman <horms@...nel.org>