All of lore.kernel.org
 help / color / mirror / Atom feed
From: Breno Leitao <leitao@debian.org>
To: Jinjie Ruan <ruanjinjie@huawei.com>
Cc: corbet@lwn.net, skhan@linuxfoundation.org,
	catalin.marinas@arm.com,  will@kernel.org, chenhuacai@kernel.org,
	kernel@xen0n.name, maddy@linux.ibm.com,  mpe@ellerman.id.au,
	npiggin@gmail.com, chleroy@kernel.org, pjw@kernel.org,
	 palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
	tglx@kernel.org,  mingo@redhat.com, bp@alien8.de,
	dave.hansen@linux.intel.com, hpa@zytor.com,  robh@kernel.org,
	saravanak@kernel.org, akpm@linux-foundation.org, bhe@redhat.com,
	 vgoyal@redhat.com, dyoung@redhat.com, rdunlap@infradead.org,
	peterz@infradead.org,  feng.tang@linux.alibaba.com,
	pawan.kumar.gupta@linux.intel.com, dapeng1.mi@linux.intel.com,
	 kees@kernel.org, elver@google.com, paulmck@kernel.org,
	lirongqing@baidu.com,  rppt@kernel.org, ardb@kernel.org,
	cfsworks@gmail.com, osandov@fb.com,  jbohac@suse.cz,
	tangyouling@kylinos.cn, sourabhjain@linux.ibm.com,
	 ritesh.list@gmail.com, eajames@linux.ibm.com,
	songshuaishuai@tinylab.org,  kevin.brodsky@arm.com,
	vishal.moola@gmail.com, junhui.liu@pigmoral.tech,
	 coxu@redhat.com, fuqiang.wang@easystack.cn,
	liaoyuanhong@vivo.com,  guoren@kernel.org,
	chenjiahao16@huawei.com, hbathini@linux.ibm.com,
	 takahiro.akashi@linaro.org, james.morse@arm.com,
	lizhengyu3@huawei.com, x86@kernel.org,
	 linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	 linux-arm-kernel@lists.infradead.org, loongarch@lists.linux.dev,
	linuxppc-dev@lists.ozlabs.org,  linux-riscv@lists.infradead.org,
	devicetree@vger.kernel.org, kexec@lists.infradead.org
Subject: Re: [PATCH v11 10/11] arm64: kexec: Add support for crashkernel CMA reservation
Date: Mon, 30 Mar 2026 02:13:57 -0700	[thread overview]
Message-ID: <aco-v4BuRSiZx7yy@gmail.com> (raw)
In-Reply-To: <20260328074013.3589544-11-ruanjinjie@huawei.com>

On Sat, Mar 28, 2026 at 03:40:12PM +0800, Jinjie Ruan wrote:
> Commit 35c18f2933c5 ("Add a new optional ",cma" suffix to the
> crashkernel= command line option") and commit ab475510e042 ("kdump:
> implement reserve_crashkernel_cma") added CMA support for kdump
> crashkernel reservation.
> 
> Crash kernel memory reservation wastes production resources if too
> large, risks kdump failure if too small, and faces allocation difficulties
> on fragmented systems due to contiguous block constraints. The new
> CMA-based crashkernel reservation scheme splits the "large fixed
> reservation" into a "small fixed region + large CMA dynamic region": the
> CMA memory is available to userspace during normal operation to avoid
> waste, and is reclaimed for kdump upon crash—saving memory while
> improving reliability.
> 
> So extend crashkernel CMA reservation support to arm64. The following
> changes are made to enable CMA reservation:
> 
> - Parse and obtain the CMA reservation size along with other crashkernel
>   parameters.
> - Call reserve_crashkernel_cma() to allocate the CMA region for kdump.
> - Include the CMA-reserved ranges for kdump kernel to use.
> - Exclude the CMA-reserved ranges from the crash kernel memory to
>   prevent them from being exported through /proc/vmcore, which is already
>   done in the crash core.
> 
> Update kernel-parameters.txt to document CMA support for crashkernel on
> arm64 architecture.
> 
> Acked-by: Catalin Marinas <catalin.marinas@arm.com>
> Acked-by: Rob Herring (Arm) <robh@kernel.org>
> Acked-by: Baoquan He <bhe@redhat.com>
> Acked-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
> Acked-by: Ard Biesheuvel <ardb@kernel.org>
> Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com>

Tested-by: Breno Leitao <leitao@debian.org>


WARNING: multiple messages have this Message-ID (diff)
From: Breno Leitao <leitao@debian.org>
To: Jinjie Ruan <ruanjinjie@huawei.com>
Cc: corbet@lwn.net, skhan@linuxfoundation.org,
	catalin.marinas@arm.com,  will@kernel.org, chenhuacai@kernel.org,
	kernel@xen0n.name, maddy@linux.ibm.com,  mpe@ellerman.id.au,
	npiggin@gmail.com, chleroy@kernel.org, pjw@kernel.org,
	 palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
	tglx@kernel.org,  mingo@redhat.com, bp@alien8.de,
	dave.hansen@linux.intel.com, hpa@zytor.com,  robh@kernel.org,
	saravanak@kernel.org, akpm@linux-foundation.org, bhe@redhat.com,
	 vgoyal@redhat.com, dyoung@redhat.com, rdunlap@infradead.org,
	peterz@infradead.org,  feng.tang@linux.alibaba.com,
	pawan.kumar.gupta@linux.intel.com, dapeng1.mi@linux.intel.com,
	 kees@kernel.org, elver@google.com, paulmck@kernel.org,
	lirongqing@baidu.com,  rppt@kernel.org, ardb@kernel.org,
	cfsworks@gmail.com, osandov@fb.com,  jbohac@suse.cz,
	tangyouling@kylinos.cn, sourabhjain@linux.ibm.com,
	 ritesh.list@gmail.com, eajames@linux.ibm.com,
	songshuaishuai@tinylab.org,  kevin.brodsky@arm.com,
	vishal.moola@gmail.com, junhui.liu@pigmoral.tech,
	 coxu@redhat.com, fuqiang.wang@easystack.cn,
	liaoyuanhong@vivo.com,  guoren@kernel.org,
	chenjiahao16@huawei.com, hbathini@linux.ibm.com,
	 takahiro.akashi@linaro.org, james.morse@arm.com,
	lizhengyu3@huawei.com, x86@kernel.org,
	 linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	 linux-arm-kernel@lists.infradead.org, loongarch@lists.linux.dev,
	linuxppc-dev@lists.ozlabs.org,  linux-riscv@lists.infradead.org,
	devicetree@vger.kernel.org, kexec@lists.infradead.org
Subject: Re: [PATCH v11 10/11] arm64: kexec: Add support for crashkernel CMA reservation
Date: Mon, 30 Mar 2026 02:13:57 -0700	[thread overview]
Message-ID: <aco-v4BuRSiZx7yy@gmail.com> (raw)
In-Reply-To: <20260328074013.3589544-11-ruanjinjie@huawei.com>

On Sat, Mar 28, 2026 at 03:40:12PM +0800, Jinjie Ruan wrote:
> Commit 35c18f2933c5 ("Add a new optional ",cma" suffix to the
> crashkernel= command line option") and commit ab475510e042 ("kdump:
> implement reserve_crashkernel_cma") added CMA support for kdump
> crashkernel reservation.
> 
> Crash kernel memory reservation wastes production resources if too
> large, risks kdump failure if too small, and faces allocation difficulties
> on fragmented systems due to contiguous block constraints. The new
> CMA-based crashkernel reservation scheme splits the "large fixed
> reservation" into a "small fixed region + large CMA dynamic region": the
> CMA memory is available to userspace during normal operation to avoid
> waste, and is reclaimed for kdump upon crash—saving memory while
> improving reliability.
> 
> So extend crashkernel CMA reservation support to arm64. The following
> changes are made to enable CMA reservation:
> 
> - Parse and obtain the CMA reservation size along with other crashkernel
>   parameters.
> - Call reserve_crashkernel_cma() to allocate the CMA region for kdump.
> - Include the CMA-reserved ranges for kdump kernel to use.
> - Exclude the CMA-reserved ranges from the crash kernel memory to
>   prevent them from being exported through /proc/vmcore, which is already
>   done in the crash core.
> 
> Update kernel-parameters.txt to document CMA support for crashkernel on
> arm64 architecture.
> 
> Acked-by: Catalin Marinas <catalin.marinas@arm.com>
> Acked-by: Rob Herring (Arm) <robh@kernel.org>
> Acked-by: Baoquan He <bhe@redhat.com>
> Acked-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
> Acked-by: Ard Biesheuvel <ardb@kernel.org>
> Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com>

Tested-by: Breno Leitao <leitao@debian.org>

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2026-04-02 12:34 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-28  7:40 [PATCH v11 00/11] arm64/riscv: Add support for crashkernel CMA reservation Jinjie Ruan
2026-03-28  7:40 ` Jinjie Ruan
2026-03-28  7:40 ` [PATCH v11 01/11] riscv: kexec_file: Fix crashk_low_res not exclude bug Jinjie Ruan
2026-03-28  7:40   ` Jinjie Ruan
2026-03-30  3:49   ` Guo Ren
2026-03-30  3:49     ` Guo Ren
2026-03-30  7:11     ` Jinjie Ruan
2026-03-30  7:11       ` Jinjie Ruan
2026-03-30  7:49       ` Guo Ren
2026-03-30  7:49         ` Guo Ren
2026-03-28  7:40 ` [PATCH v11 02/11] powerpc/crash: Fix possible memory leak in update_crash_elfcorehdr() Jinjie Ruan
2026-03-28  7:40   ` Jinjie Ruan
2026-03-28  7:40 ` [PATCH v11 03/11] x86/kexec: Fix potential buffer overflow in prepare_elf_headers() Jinjie Ruan
2026-03-28  7:40   ` Jinjie Ruan
2026-03-28  7:40 ` [PATCH v11 04/11] arm64: kexec_file: " Jinjie Ruan
2026-03-28  7:40   ` Jinjie Ruan
2026-03-28  7:40 ` [PATCH v11 05/11] riscv: " Jinjie Ruan
2026-03-28  7:40   ` Jinjie Ruan
2026-03-30  3:47   ` Guo Ren
2026-03-30  3:47     ` Guo Ren
2026-03-28  7:40 ` [PATCH v11 06/11] LoongArch: kexec: " Jinjie Ruan
2026-03-28  7:40   ` Jinjie Ruan
2026-03-28  7:40 ` [PATCH v11 07/11] powerpc/crash: sort crash memory ranges before preparing elfcorehdr Jinjie Ruan
2026-03-28  7:40   ` Jinjie Ruan
2026-03-28  7:40 ` [PATCH v11 08/11] crash: Exclude crash kernel memory in crash core Jinjie Ruan
2026-03-28  7:40   ` Jinjie Ruan
2026-03-28  7:40 ` [PATCH v11 09/11] crash: Use crash_exclude_core_ranges() on powerpc Jinjie Ruan
2026-03-28  7:40   ` Jinjie Ruan
2026-03-28  7:40 ` [PATCH v11 10/11] arm64: kexec: Add support for crashkernel CMA reservation Jinjie Ruan
2026-03-28  7:40   ` Jinjie Ruan
2026-03-30  9:13   ` Breno Leitao [this message]
2026-03-30  9:13     ` Breno Leitao
2026-03-28  7:40 ` [PATCH v11 11/11] riscv: " Jinjie Ruan
2026-03-28  7:40   ` Jinjie Ruan

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=aco-v4BuRSiZx7yy@gmail.com \
    --to=leitao@debian.org \
    --cc=akpm@linux-foundation.org \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=ardb@kernel.org \
    --cc=bhe@redhat.com \
    --cc=bp@alien8.de \
    --cc=catalin.marinas@arm.com \
    --cc=cfsworks@gmail.com \
    --cc=chenhuacai@kernel.org \
    --cc=chenjiahao16@huawei.com \
    --cc=chleroy@kernel.org \
    --cc=corbet@lwn.net \
    --cc=coxu@redhat.com \
    --cc=dapeng1.mi@linux.intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dyoung@redhat.com \
    --cc=eajames@linux.ibm.com \
    --cc=elver@google.com \
    --cc=feng.tang@linux.alibaba.com \
    --cc=fuqiang.wang@easystack.cn \
    --cc=guoren@kernel.org \
    --cc=hbathini@linux.ibm.com \
    --cc=hpa@zytor.com \
    --cc=james.morse@arm.com \
    --cc=jbohac@suse.cz \
    --cc=junhui.liu@pigmoral.tech \
    --cc=kees@kernel.org \
    --cc=kernel@xen0n.name \
    --cc=kevin.brodsky@arm.com \
    --cc=kexec@lists.infradead.org \
    --cc=liaoyuanhong@vivo.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=lirongqing@baidu.com \
    --cc=lizhengyu3@huawei.com \
    --cc=loongarch@lists.linux.dev \
    --cc=maddy@linux.ibm.com \
    --cc=mingo@redhat.com \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.com \
    --cc=osandov@fb.com \
    --cc=palmer@dabbelt.com \
    --cc=paulmck@kernel.org \
    --cc=pawan.kumar.gupta@linux.intel.com \
    --cc=peterz@infradead.org \
    --cc=pjw@kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=ritesh.list@gmail.com \
    --cc=robh@kernel.org \
    --cc=rppt@kernel.org \
    --cc=ruanjinjie@huawei.com \
    --cc=saravanak@kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=songshuaishuai@tinylab.org \
    --cc=sourabhjain@linux.ibm.com \
    --cc=takahiro.akashi@linaro.org \
    --cc=tangyouling@kylinos.cn \
    --cc=tglx@kernel.org \
    --cc=vgoyal@redhat.com \
    --cc=vishal.moola@gmail.com \
    --cc=will@kernel.org \
    --cc=x86@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.