From: sashiko-bot@kernel.org
To: robh@kernel.org, baoquan.he@linux.dev, rppt@kernel.org,
"Wandun Chen" <chenwandun1@gmail.com>,
m.szyprowski@samsung.com
Cc: mingo@redhat.com, saravanak@kernel.org, pjw@kernel.org,
linux-riscv@lists.infradead.org, pasha.tatashin@soleen.com,
kernel@xen0n.name, iommu@lists.linux.dev, ruirui.yang@linux.dev,
tglx@kernel.org, devicetree@vger.kernel.org, palmer@dabbelt.com,
aou@eecs.berkeley.edu, catalin.marinas@arm.com,
dave.hansen@linux.intel.com, loongarch@lists.linux.dev,
robin.murphy@arm.com, linux-kernel@vger.kernel.org, bp@alien8.de,
pratyush@kernel.org, alex@ghiti.fr, chenhuacai@kernel.org,
linux-arm-kernel@lists.infradead.org, hpa@zytor.com,
linux-mm@kvack.org, kexec@lists.infradead.org,
mark.rutland@arm.com, x86@kernel.org, akpm@linux-foundation.org,
conor+dt@kernel.org, will@kernel.org
Subject: Re: [PATCH v7 6/9] of: reserved_mem: add dumpable flag to opt-in vmcore
Date: Tue, 22 Sep 2026 08:54:08 +0000 [thread overview]
Message-ID: <20260922085409.18A301F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260922084256.1515554-7-chenwandun1@gmail.com>
> From: Wandun Chen <chenwandun@lixiang.com>
>
> Add a 'dumpable' flag to struct reserved_mem to decide whether a
> reserved area should be included in the kdump vmcore. Non-dumpable
> regions are later marked MEMBLOCK_NODUMP;the filtering itself happens
> in memblock, keeping the arch kdump code independent of the DT API.
>
> Most reserved regions are owned by devices and do not contain data
> useful for kernel crash analysis, so dumpable default to false.
> Reusable CMA regions are different: their pages are handed back to the
> buddy allocator and may contain key data for crash analysis, so set
> dumpable to true in rmem_cma_setup().
>
> The dumpable flag is also used to check /memreserve/ entries for overlap
> with other dumpable regions.
>
> Suggested-by: Rob Herring <robh@kernel.org>
> Signed-off-by: Wandun Chen <chenwandun@lixiang.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260922084256.1515554-1-chenwandun1@gmail.com?part=6
WARNING: multiple messages have this Message-ID (diff)
From: sashiko-bot@kernel.org
To: robh@kernel.org, baoquan.he@linux.dev, rppt@kernel.org,
"Wandun Chen" <chenwandun1@gmail.com>,
m.szyprowski@samsung.com
Cc: mingo@redhat.com, saravanak@kernel.org, pjw@kernel.org,
linux-riscv@lists.infradead.org, pasha.tatashin@soleen.com,
kernel@xen0n.name, iommu@lists.linux.dev, ruirui.yang@linux.dev,
tglx@kernel.org, devicetree@vger.kernel.org, palmer@dabbelt.com,
aou@eecs.berkeley.edu, catalin.marinas@arm.com,
dave.hansen@linux.intel.com, loongarch@lists.linux.dev,
robin.murphy@arm.com, linux-kernel@vger.kernel.org, bp@alien8.de,
pratyush@kernel.org, alex@ghiti.fr, chenhuacai@kernel.org,
linux-arm-kernel@lists.infradead.org, hpa@zytor.com,
linux-mm@kvack.org, kexec@lists.infradead.org,
mark.rutland@arm.com, x86@kernel.org, akpm@linux-foundation.org,
conor+dt@kernel.org, will@kernel.org
Subject: Re: [PATCH v7 6/9] of: reserved_mem: add dumpable flag to opt-in vmcore
Date: Tue, 22 Sep 2026 08:54:08 +0000 [thread overview]
Message-ID: <20260922085409.18A301F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260922084256.1515554-7-chenwandun1@gmail.com>
> From: Wandun Chen <chenwandun@lixiang.com>
>
> Add a 'dumpable' flag to struct reserved_mem to decide whether a
> reserved area should be included in the kdump vmcore. Non-dumpable
> regions are later marked MEMBLOCK_NODUMP;the filtering itself happens
> in memblock, keeping the arch kdump code independent of the DT API.
>
> Most reserved regions are owned by devices and do not contain data
> useful for kernel crash analysis, so dumpable default to false.
> Reusable CMA regions are different: their pages are handed back to the
> buddy allocator and may contain key data for crash analysis, so set
> dumpable to true in rmem_cma_setup().
>
> The dumpable flag is also used to check /memreserve/ entries for overlap
> with other dumpable regions.
>
> Suggested-by: Rob Herring <robh@kernel.org>
> Signed-off-by: Wandun Chen <chenwandun@lixiang.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260922084256.1515554-1-chenwandun1@gmail.com?part=6
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-09-22 8:54 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 8:42 [PATCH v7 0/9] kdump: reduce vmcore size and capture time Wandun Chen
2026-09-22 8:42 ` Wandun Chen
2026-09-22 8:42 ` [PATCH v7 1/9] riscv: build crash_mem ranges from memblock instead of resource tree Wandun Chen
2026-09-22 8:42 ` Wandun Chen
2026-09-22 8:59 ` sashiko-bot
2026-09-22 8:59 ` sashiko-bot
2026-09-22 8:42 ` [PATCH v7 2/9] crash_core: fold duplicated memblock arch hooks into the weak default Wandun Chen
2026-09-22 8:42 ` Wandun Chen
2026-09-22 8:56 ` sashiko-bot
2026-09-22 8:56 ` sashiko-bot
2026-09-22 8:42 ` [PATCH v7 3/9] crash_core: serialize crash header preparation against hotplug Wandun Chen
2026-09-22 8:42 ` Wandun Chen
2026-09-22 9:03 ` sashiko-bot
2026-09-22 9:03 ` sashiko-bot
2026-09-22 8:42 ` [PATCH v7 4/9] crash_core: replace for_each_mem_range() with for_each_mem_region() Wandun Chen
2026-09-22 8:42 ` Wandun Chen
2026-09-22 8:56 ` sashiko-bot
2026-09-22 8:56 ` sashiko-bot
2026-09-22 8:42 ` [PATCH v7 5/9] memblock: introduce MEMBLOCK_NODUMP flag Wandun Chen
2026-09-22 8:42 ` Wandun Chen
2026-09-22 9:02 ` sashiko-bot
2026-09-22 9:02 ` sashiko-bot
2026-09-22 8:42 ` [PATCH v7 6/9] of: reserved_mem: add dumpable flag to opt-in vmcore Wandun Chen
2026-09-22 8:42 ` Wandun Chen
2026-09-22 8:54 ` sashiko-bot [this message]
2026-09-22 8:54 ` sashiko-bot
2026-09-22 8:42 ` [PATCH v7 7/9] of: reserved_mem: mark /reserved-memory entries with MEMBLOCK_NODUMP Wandun Chen
2026-09-22 8:42 ` Wandun Chen
2026-09-22 9:01 ` sashiko-bot
2026-09-22 9:01 ` sashiko-bot
2026-09-22 8:42 ` [PATCH v7 8/9] of: reserved_mem: mark /memreserve/ entries as MEMBLOCK_NODUMP Wandun Chen
2026-09-22 8:42 ` Wandun Chen
2026-09-22 9:04 ` sashiko-bot
2026-09-22 9:04 ` sashiko-bot
2026-09-22 8:42 ` [PATCH v7 9/9] crash_core: skip MEMBLOCK_NODUMP regions when building vmcore ELF header Wandun Chen
2026-09-22 8:42 ` Wandun Chen
2026-09-22 9:02 ` sashiko-bot
2026-09-22 9:02 ` sashiko-bot
2026-10-02 8:17 ` [PATCH v7 0/9] kdump: reduce vmcore size and capture time Mike Rapoport
2026-10-02 8:17 ` Mike Rapoport
2026-10-09 3:04 ` Wandun
2026-10-09 3:04 ` Wandun
2026-10-09 16:26 ` Mike Rapoport
2026-10-09 16:26 ` Mike Rapoport
2026-10-09 17:10 ` Rob Herring
2026-10-09 17:10 ` Rob Herring
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=20260922085409.18A301F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=baoquan.he@linux.dev \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=chenhuacai@kernel.org \
--cc=chenwandun1@gmail.com \
--cc=conor+dt@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=hpa@zytor.com \
--cc=iommu@lists.linux.dev \
--cc=kernel@xen0n.name \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=loongarch@lists.linux.dev \
--cc=m.szyprowski@samsung.com \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=palmer@dabbelt.com \
--cc=pasha.tatashin@soleen.com \
--cc=pjw@kernel.org \
--cc=pratyush@kernel.org \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.com \
--cc=rppt@kernel.org \
--cc=ruirui.yang@linux.dev \
--cc=saravanak@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=tglx@kernel.org \
--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.