From: Dave Young <ruirui.yang@linux.dev>
To: "David Hildenbrand (Arm)" <david@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Baoquan He <baoquan.he@linux.dev>,
David Carlier <devnexen@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
kexec@lists.infradead.org
Subject: Re: [PATCH] vmcoreinfo: export SECTION_HAS_MEM_MAP
Date: Mon, 28 Sep 2026 18:23:03 +0800 [thread overview]
Message-ID: <9c47dad9-2716-4ae0-b6e2-9e6b5c718859@linux.dev> (raw)
In-Reply-To: <20260928-section_has_mem_map-v1-1-4129f6ba2838@kernel.org>
On 9/28/26 4:48 PM, David Hildenbrand (Arm) wrote:
> The crash tool currently hardcodes SECTION_HAS_MEM_MAP, and makedumpfile
> needs similar information (although still relying on
> SECTION_MARKED_PRESENT, it should switch to SECTION_HAS_MEM_MAP).
>
> Let's just export the value instead, so tools that work on vmcoreinfo
> will not have to guess.
>
> Signed-off-by: David Hildenbrand (Arm) <david@kernel.org>
> ---
> Result of the discussion in reply to "[PATCH v2 00/13] mm/sparse: remove
> SECTION_MARKED_PRESENT and further cleanups" [1]
>
> This patch can go in independently. It would be preferable if both
> go into the same kernel release ;)
>
> [1] https://lore.kernel.org/r/20260921-b4-sparsemem_cleanups-v2-0-54d81d65e125@kernel.org
> ---
> kernel/vmcore_info.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/kernel/vmcore_info.c b/kernel/vmcore_info.c
> index 5a417f8a922a..7833a36064a8 100644
> --- a/kernel/vmcore_info.c
> +++ b/kernel/vmcore_info.c
> @@ -182,6 +182,7 @@ static int __init crash_save_vmcoreinfo_init(void)
> VMCOREINFO_STRUCT_SIZE(mem_section);
> VMCOREINFO_OFFSET(mem_section, section_mem_map);
> VMCOREINFO_NUMBER(SECTION_SIZE_BITS);
> + VMCOREINFO_NUMBER(SECTION_HAS_MEM_MAP);
> VMCOREINFO_NUMBER(MAX_PHYSMEM_BITS);
> #endif
> VMCOREINFO_STRUCT_SIZE(page);
Current crash code looks below:
#define SECTION_MARKED_PRESENT (1UL<<0)
#define SECTION_HAS_MEM_MAP (1UL<<1)
#define SECTION_IS_ONLINE (1UL<<2)
#define SECTION_IS_EARLY (1UL<<3)
#define SECTION_TAINT_ZONE_DEVICE (1UL<<4)
#define SECTION_MAP_LAST_BIT (1UL<<5)
#define SECTION_MAP_MASK (~(SECTION_MAP_LAST_BIT-1))
And it does not match the kernel for below chunk with ifdef
#ifdef CONFIG_ZONE_DEVICE
SECTION_TAINT_ZONE_DEVICE_BIT,
#endif
#ifdef CONFIG_SPARSEMEM_VMEMMAP_PREINIT
SECTION_IS_VMEMMAP_PREINIT_BIT,
#endif
The last bit could be wrong in crash. So all numbers should be exported in vmcoreinfo.
Thoughts?
ThanksDave
next prev parent reply other threads:[~2026-09-28 10:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 8:48 [PATCH] vmcoreinfo: export SECTION_HAS_MEM_MAP David Hildenbrand (Arm)
2026-09-28 9:11 ` Baoquan He
2026-09-28 9:14 ` David Hildenbrand (Arm)
2026-09-28 10:12 ` Baoquan He
2026-09-28 10:23 ` Dave Young [this message]
2026-09-28 11:42 ` David Hildenbrand (Arm)
2026-09-29 0:25 ` Dave Young
2026-09-29 2:02 ` HAGIO KAZUHITO(萩尾 一仁)
2026-09-29 6:16 ` David Hildenbrand (Arm)
2026-09-28 15:53 ` Bradley Morgan
2026-09-29 5:05 ` Anshuman Khandual
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=9c47dad9-2716-4ae0-b6e2-9e6b5c718859@linux.dev \
--to=ruirui.yang@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=baoquan.he@linux.dev \
--cc=david@kernel.org \
--cc=devnexen@gmail.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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.