From: "David Hildenbrand (Arm)" <david@kernel.org>
To: "HAGIO KAZUHITO(萩尾 一仁)" <kazuhito.hagio@nec.com>,
"Dave Young" <ruirui.yang@linux.dev>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Baoquan He" <baoquan.he@linux.dev>,
"David Carlier" <devnexen@gmail.com>, "Tao Liu" <ltao@redhat.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"kexec@lists.infradead.org" <kexec@lists.infradead.org>
Subject: Re: [PATCH] vmcoreinfo: export SECTION_HAS_MEM_MAP
Date: Tue, 29 Sep 2026 08:16:52 +0200 [thread overview]
Message-ID: <c52362f5-60b6-4bf8-8b32-73269a0db93a@kernel.org> (raw)
In-Reply-To: <9d1f8623-c14f-4e51-8aee-6971a4cfbd31@nec.com>
On 9/29/26 04:02, HAGIO KAZUHITO(萩尾 一仁) wrote:
>
>
> On 2026/09/29 9:25, Dave Young wrote:
>> On 9/28/26 7:42 PM, David Hildenbrand (Arm) wrote:
>>>
>>> You know the crash code best, so likely ... it's time one of the crash people
>>> takes over this patch?
>>
>> Rethinking about it I'm hesitating to add many more to vmcoreinfo although it is reasonable, about the #ifdef things, there are other places other than mm, crash can not depend on the /proc/config.gz which is not reliable in the old kernel memory, maybe it will be helpful to export another elf note for old kernel's kconfig. So I'd like to support to use your patch for the time being as the first bit is always needed and leave the remaining concerns a follow up item.
>
> I agree, from makedumpfile's view point.
>
> (to be exact, makedumpfile needs this but maybe crash can read enum values from vmlinux.)
That's a good point, maybe that indeed works for crash.
--
Cheers,
David
next prev parent reply other threads:[~2026-09-29 6:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 8:48 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
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) [this message]
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=c52362f5-60b6-4bf8-8b32-73269a0db93a@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=baoquan.he@linux.dev \
--cc=devnexen@gmail.com \
--cc=kazuhito.hagio@nec.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ltao@redhat.com \
--cc=ruirui.yang@linux.dev \
/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®