From: Wandun <chenwandun1@gmail.com>
To: Baoquan He <baoquan.he@linux.dev>, Mike Rapoport <rppt@kernel.org>
Cc: catalin.marinas@arm.com, will@kernel.org, chenhuacai@kernel.org,
pjw@kernel.org, palmer@dabbelt.com, aou@eecs.berkeley.edu,
tglx@kernel.org, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, x86@kernel.org, robh@kernel.org,
saravanak@kernel.org, akpm@linux-foundation.org,
pasha.tatashin@soleen.com, pratyush@kernel.org,
m.szyprowski@samsung.com, mark.rutland@arm.com,
kernel@xen0n.name, alex@ghiti.fr, hpa@zytor.com,
ruirui.yang@linux.dev, robin.murphy@arm.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, loongarch@lists.linux.dev,
linux-riscv@lists.infradead.org, devicetree@vger.kernel.org,
kexec@lists.infradead.org, linux-mm@kvack.org,
iommu@lists.linux.dev
Subject: Re: [PATCH v6 06/10] memblock: introduce MEMBLOCK_NODUMP flag
Date: Sun, 20 Sep 2026 16:00:30 +0800 [thread overview]
Message-ID: <32b00102-0961-49e3-b780-74d6db182809@gmail.com> (raw)
In-Reply-To: <aq9UGXeqmCfuPHdD@fedora>
On 9/20/26 11:33, Baoquan He wrote:
> On 09/19/26 at 10:11am, Mike Rapoport wrote:
>> On Fri, Sep 18, 2026 at 04:08:10PM +0800, Baoquan He wrote:
>>> On 09/02/26 at 03:31pm, Wandun Chen wrote:
> ...snip...
>>>> +/**
>>>> + * memblock_mark_nodump - Mark a memory region with flag MEMBLOCK_NODUMP.
>>>> + * @base: the base phys addr of the region
>>>> + * @size: the size of the region
>>>> + *
>>>> + * Mark the region as not to be included in crash dumps.
>>>> + *
>>>> + * Return: 0 on success, -errno on failure.
>>>> + */
>>>> +int __init_memblock memblock_mark_nodump(phys_addr_t base, phys_addr_t size)
>>> ~~~~~~~~~~~~~~^
>>> Is it impossible to use at runtime even thought it claims to be generic?
>>
>> This should only happen at boot.
>>
>> Allowing modifications of memblock properties in runtime is a can of worms
>> I don't want to open.
>
> Thank you. This is why I said this can't be claimed as a generic way to
> mark memory region as no dump. The generic way I'd like to see is
> at any time of system we can mark any unwanted memory region as no dump.
> And it won't impact the behaviour of the current system.
Thanks Mike for the explanation and Baoquan for the suggestion.
I'll drop the "generic" related description in the next version.
Baoquan, by the way, patch 2 is still awaiting review. It rewrites
the riscv side of the code that patch 3 (which you've acked) then
folds into the weak defaults, if you could take a look at it too,
that would be very helpful.
Best regards,
Wandun
>
>>
>>>> +{
>>>> + return memblock_setclr_flag(&memblock.memory, base, size, 1,
>>>> + MEMBLOCK_NODUMP);
>>>> +}
>>>> +
>>>> static bool should_skip_region(struct memblock_type *type,
>>>> struct memblock_region *m,
>>>> int nid, int flags)
>>>> @@ -2887,6 +2902,7 @@ static const char * const flagname[] = {
>>>> [ilog2(MEMBLOCK_RSRV_KERN)] = "RSV_KERN",
>>>> [ilog2(MEMBLOCK_KHO_SCRATCH)] = "KHO_SCRATCH",
>>>> [ilog2(MEMBLOCK_RSRV_HUGETLB)] = "RSV_HUGETLB",
>>>> + [ilog2(MEMBLOCK_NODUMP)] = "NODUMP",
>>>> };
>>>>
>>>> static int memblock_debug_show(struct seq_file *m, void *private)
>>>> --
>>>> 2.43.0
>>>>
>>
>> --
>> Sincerely yours,
>> Mike.
next prev parent reply other threads:[~2026-09-20 8:00 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 7:31 [PATCH v6 00/10] kdump: reduce vmcore size and capture time Wandun Chen
2026-09-02 7:31 ` [PATCH v6 01/10] mm: memblock: add missing HugeTLB flag name Wandun Chen
2026-09-14 5:20 ` Mike Rapoport
2026-09-15 12:49 ` Wandun
2026-09-02 7:31 ` [PATCH v6 02/10] riscv: build crash_mem ranges from memblock instead of resource tree Wandun Chen
2026-09-02 7:31 ` [PATCH v6 03/10] crash_core: fold duplicated memblock arch hooks into the weak default Wandun Chen
2026-09-18 7:30 ` Baoquan He
2026-09-18 8:45 ` Wandun
2026-09-18 8:48 ` Baoquan He
2026-09-02 7:31 ` [PATCH v6 04/10] crash_core: serialize crash header preparation against hotplug Wandun Chen
2026-09-18 7:54 ` Baoquan He
2026-09-02 7:31 ` [PATCH v6 05/10] crash_core: replace for_each_mem_range() with for_each_mem_region() Wandun Chen
2026-09-18 8:04 ` Baoquan He
2026-09-02 7:31 ` [PATCH v6 06/10] memblock: introduce MEMBLOCK_NODUMP flag Wandun Chen
2026-09-18 7:00 ` Mike Rapoport
2026-09-18 8:08 ` Baoquan He
2026-09-18 8:22 ` Wandun
2026-09-19 7:11 ` Mike Rapoport
2026-09-20 3:33 ` Baoquan He
2026-09-20 8:00 ` Wandun [this message]
2026-09-02 7:31 ` [PATCH v6 07/10] of: reserved_mem: add dumpable flag to opt-in vmcore Wandun Chen
2026-09-17 21:56 ` Rob Herring (Arm)
2026-09-02 7:31 ` [PATCH v6 08/10] of: reserved_mem: mark /reserved-memory entries with MEMBLOCK_NODUMP Wandun Chen
2026-09-03 7:32 ` Marek Szyprowski
2026-09-17 21:56 ` Rob Herring (Arm)
2026-09-02 7:31 ` [PATCH v6 09/10] of: reserved_mem: mark /memreserve/ entries as MEMBLOCK_NODUMP Wandun Chen
2026-09-03 7:32 ` Marek Szyprowski
2026-09-02 7:31 ` [PATCH v6 10/10] crash_core: skip MEMBLOCK_NODUMP regions when building vmcore ELF header Wandun Chen
2026-09-18 8:09 ` Baoquan He
2026-09-02 8:53 ` [PATCH v6 00/10] kdump: reduce vmcore size and capture time Baoquan He
2026-09-03 7:05 ` Wandun
2026-09-03 7:31 ` Baoquan He
2026-09-03 7:43 ` Wandun
2026-09-03 9:38 ` Baoquan He
2026-09-04 11:08 ` Chen Wandun
2026-09-15 13:01 ` Wandun
2026-09-18 7:03 ` Mike Rapoport
2026-09-18 7:31 ` Baoquan He
2026-09-18 8:17 ` Baoquan He
2026-09-18 10:53 ` Wandun
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=32b00102-0961-49e3-b780-74d6db182809@gmail.com \
--to=chenwandun1@gmail.com \
--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=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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®