[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZKD3tEBknEiF4PZK@MiWiFi-R3L-srv>
Date: Sun, 2 Jul 2023 12:06:12 +0800
From: Baoquan He <bhe@...hat.com>
To: "chenjiahao (C)" <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, thunder.leizhen@...wei.com, horms@...nel.org
Subject: Re: [PATCH -next v5 1/2] riscv: kdump: Implement
crashkernel=X,[high,low]
On 07/01/23 at 05:51pm, chenjiahao (C) wrote:
......
> I have sent v6 patches, implementing the logic above. That fixes the
> retrying
>
> logic and should be aligned with Arm64 code.
Hmm, it has improved much, while there's still issue which need be
fixed. You missed the case that crsahkernel low is specified as zero
explicitly. Obviously your v6 is not able to handle that well. Means
your v6 is not aligned with the current arm64 code completely.
crashkernel=xM,high crashkernel=0M,low
>
>
> Please let me know if there is any problem remains.
Earlier, I posted below RFC patchset to try to unify the
crashkernel=,high support on x86, arm64 and risc-v, the generic arch.
Wondering what you think about it. risc-v can be added in with very few
change to get the crahskernel=,high support.
[RFC PATCH 0/4] kdump: add generic functions to simplify crashkernel crashkernel in architecture
Surely, the crashkernel=,high support can be added independently in
advance. Later my patchset can unify them and remove the duplicated code
in risc-v. It's up to you and risc-v maintainers/reivewers to take one.
Anyway, I will add comment to your v6 to point out the issue.
Thanks
Baoquan
Powered by blists - more mailing lists