[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190416131549.GD31772@zn.tnic>
Date: Tue, 16 Apr 2019 15:15:49 +0200
From: Borislav Petkov <bp@...en8.de>
To: Chen Zhou <chenzhou10@...wei.com>
Cc: tglx@...utronix.de, mingo@...hat.com, ebiederm@...ssion.com,
rppt@...ux.ibm.com, catalin.marinas@....com, will.deacon@....com,
akpm@...ux-foundation.org, ard.biesheuvel@...aro.org,
horms@...ge.net.au, takahiro.akashi@...aro.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
kexec@...ts.infradead.org, linux-mm@...ck.org,
wangkefeng.wang@...wei.com
Subject: Re: [RESEND PATCH v5 0/4] support reserving crashkernel above 4G on
arm64 kdump
On Tue, Apr 16, 2019 at 07:35:15PM +0800, Chen Zhou wrote:
> When crashkernel is reserved above 4G in memory, kernel should reserve
> some amount of low memory for swiotlb and some DMA buffers. So there may
> be two crash kernel regions, one is below 4G, the other is above 4G.
>
> Crash dump kernel reads more than one crash kernel regions via a dtb
> property under node /chosen,
> linux,usable-memory-range = <BASE1 SIZE1 [BASE2 SIZE2]>.
Can you please not flood everyone with this patchset every day, and
today twice?
This is not the frequency with how you send patchsets upstream. See
https://www.kernel.org/doc/html/latest/process/submitting-patches.html#don-t-get-discouraged-or-impatient
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
Powered by blists - more mailing lists