[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAJF2gTQ-aRfpK_Ct7pbTcgBEU9qkTAr9VG8B66G0NDBmchSYtA@mail.gmail.com>
Date: Tue, 11 Apr 2023 09:38:18 +0800
From: Guo Ren <guoren@...nel.org>
To: Simon Horman <horms@...nel.org>
Cc: Chen Jiahao <chenjiahao16@...wei.com>,
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, 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 v3 1/2] riscv: kdump: Implement crashkernel=X,[high,low]
On Fri, Apr 7, 2023 at 8:03 PM Simon Horman <horms@...nel.org> wrote:
>
> On Fri, Apr 07, 2023 at 05:06:24PM +0800, Guo Ren wrote:
> > On Thu, Apr 6, 2023 at 10:06 PM Chen Jiahao <chenjiahao16@...wei.com> 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".
> > Asked-by: Guo Ren <guoren@...nel.org>
>
> Perhaps 'Acked-by' :)
Sorry, my typo.
Acked-by: Guo Ren <guoren@...nel.org>
--
Best Regards
Guo Ren
Powered by blists - more mailing lists