Thread (66 messages) 66 messages, 8 authors, 2021-12-21

Re: [PATCH v17 02/10] x86: kdump: make the lower bound of crash kernel reservation consistent

flat view

From: Catalin Marinas <catalin.marinas@arm.com>
Date: 2021-12-14 19:24:29
Also in: kexec, linux-arm-kernel, linux-doc, lkml

On Tue, Dec 14, 2021 at 08:07:58PM +0100, Borislav Petkov wrote:
On Fri, Dec 10, 2021 at 02:55:25PM +0800, Zhen Lei wrote:
quoted
From: Chen Zhou <redacted>

The lower bounds of crash kernel reservation and crash kernel low
reservation are different, use the consistent value CRASH_ALIGN.
A big WHY is missing here to explain why the lower bound of the
allocation range needs to be 16M and why was 0 wrong?
I asked the same here:

https://lore.kernel.org/r/20210224143547.GB28965@arm.com (local)

IIRC Baoquan said that there is a 1MB reserved for x86 anyway in the
lower part, so that's equivalent in practice to starting from
CRASH_ALIGN.

Anyway, I agree the commit log should describe this.

-- 
Catalin
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help