From: Baoquan He <bhe@redhat.com>
To: Mingzheng Xing <xingmingzheng@iscas.ac.cn>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable@vger.kernel.org, Chen Jiahao <chenjiahao16@huawei.com>
Subject: Re: [PATCH v2] Revert "riscv: kdump: fix crashkernel reserving problem on RISC-V"
Date: Tue, 30 Apr 2024 11:39:49 +0800 [thread overview]
Message-ID: <ZjBoBYwdPMyPDGhG@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20240430032403.19562-1-xingmingzheng@iscas.ac.cn>
On 04/30/24 at 11:24am, Mingzheng Xing wrote:
> This reverts commit 1d6cd2146c2b58bc91266db1d5d6a5f9632e14c0 which was
> mistakenly added into v6.6.y and the commit corresponding to the 'Fixes:'
> tag is invalid. For more information, see link [1].
>
> This will result in the loss of Crashkernel data in /proc/iomem, and kdump
> failed:
>
> ```
> Memory for crashkernel is not reserved
> Please reserve memory by passing"crashkernel=Y@X" parameter to kernel
> Then try to loading kdump kernel
> ```
>
> After revert, kdump works fine. Tested on QEMU riscv.
>
> Link: https://lore.kernel.org/linux-riscv/ZSiQRDGLZk7lpakE@MiWiFi-R3L-srv [1]
> Cc: Baoquan He <bhe@redhat.com>
> Cc: Chen Jiahao <chenjiahao16@huawei.com>
> Signed-off-by: Mingzheng Xing <xingmingzheng@iscas.ac.cn>
Ack. This is necessary for v6.6.y stable branch.
Acked-by: Baoquan He <bhe@redhat.com>
> ---
>
> v1 -> v2:
>
> - Changed the commit message
> - Added Cc:
>
> v1:
> https://lore.kernel.org/stable/20240416085647.14376-1-xingmingzheng@iscas.ac.cn
>
> arch/riscv/kernel/setup.c | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/arch/riscv/kernel/setup.c b/arch/riscv/kernel/setup.c
> index aac853ae4eb74..e600aab116a40 100644
> --- a/arch/riscv/kernel/setup.c
> +++ b/arch/riscv/kernel/setup.c
> @@ -173,6 +173,19 @@ static void __init init_resources(void)
> if (ret < 0)
> goto error;
>
> +#ifdef CONFIG_KEXEC_CORE
> + if (crashk_res.start != crashk_res.end) {
> + ret = add_resource(&iomem_resource, &crashk_res);
> + if (ret < 0)
> + goto error;
> + }
> + if (crashk_low_res.start != crashk_low_res.end) {
> + ret = add_resource(&iomem_resource, &crashk_low_res);
> + if (ret < 0)
> + goto error;
> + }
> +#endif
> +
> #ifdef CONFIG_CRASH_DUMP
> if (elfcorehdr_size > 0) {
> elfcorehdr_res.start = elfcorehdr_addr;
> --
> 2.34.1
>
next prev parent reply other threads:[~2024-04-30 3:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 3:24 [PATCH v2] Revert "riscv: kdump: fix crashkernel reserving problem on RISC-V" Mingzheng Xing
2024-04-30 3:39 ` Baoquan He [this message]
2024-04-30 3:51 ` Mingzheng Xing
2024-04-30 7:54 ` Greg Kroah-Hartman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZjBoBYwdPMyPDGhG@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=chenjiahao16@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=xingmingzheng@iscas.ac.cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox