[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZB3ZEBRKlCI9WIgK@arm.com>
Date: Fri, 24 Mar 2023 17:08:32 +0000
From: Catalin Marinas <catalin.marinas@....com>
To: Baoquan He <bhe@...hat.com>
Cc: linux-kernel@...r.kernel.org, horms@...nel.org,
thunder.leizhen@...wei.com, John.p.donnelly@...cle.com,
will@...nel.org, kexec@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v4] arm64: kdump: simplify the reservation behaviour of
crashkernel=,high
On Fri, Mar 24, 2023 at 10:08:17PM +0800, Baoquan He wrote:
> On 03/23/23 at 05:25pm, Catalin Marinas wrote:
> > On Mon, Mar 20, 2023 at 09:12:08PM +0800, Baoquan He wrote:
> > > crashkernel=size
> > > 1)first attempt: low memory under arm64_dma_phys_limit
> > > 2)fallback: finding memory above 4G
> >
> > (2) should be 'finding memory above arm64_dma_phys_limit' to keep the
> > current behaviour for RPi4.
>
> Then for RPi4, with case 2), it will find memory above
> arm64_dma_phys_limit, namely 1G. Then it will get two memory regions,
> one could be in [1G, 4G], another is below 4G. I am fine with this, as
> long as it won't cause confusion that people may think two low memory
> regions you mentioned earlier. Please help confirm if I understand your
> suggestioin correctly. I will start making patch with this clarified.
Yes, you understood correctly. While it may still be slightly confusing,
if the user is not specific about high and low on the cmdline, we just
allow the kernel to find the best places. I assume distros will just use
,high and get a consistent behaviour on all platforms.
--
Catalin
Powered by blists - more mailing lists