From: Andrew Morton <akpm@linux-foundation.org>
To: Sourabh Jain <sourabhjain@linux.ibm.com>
Cc: linux-kernel@vger.kernel.org,
Aditya Gupta <adityag@linux.ibm.com>, Baoquan he <bhe@redhat.com>,
Dave Young <dyoung@redhat.com>,
Hari Bathini <hbathini@linux.ibm.com>,
Jiri Bohac <jbohac@suse.cz>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Mahesh J Salgaonkar <mahesh@linux.ibm.com>,
Pingfan Liu <piliu@redhat.com>,
"Ritesh Harjani (IBM)" <ritesh.list@gmail.com>,
Shivang Upadhyay <shivangu@linux.ibm.com>,
Sourabh Jain <sourabhjains@linux.ibm.com>,
Vivek Goyal <vgoyal@redhat.com>,
linuxppc-dev@lists.ozlabs.org, kexec@lists.infradea
Subject: Re: [PATCH v4 0/5] kexec: reorganize sysfs interface and add new kexec sysfs
Date: Fri, 14 Nov 2025 15:25:50 -0800 [thread overview]
Message-ID: <20251114152550.ac2dd5e23542f09c62defec7@linux-foundation.org> (raw)
In-Reply-To: <20251114051504.614937-1-sourabhjain@linux.ibm.com>
On Fri, 14 Nov 2025 10:44:59 +0530 Sourabh Jain <sourabhjain@linux.ibm.com> wrote:
> All existing kexec and kdump sysfs entries are moved to a new location,
> /sys/kernel/kexec, to keep /sys/kernel/ clean and better organized.
> Symlinks are created at the old locations for backward compatibility and
> can be removed in the future [02/05].
>
> While doing this cleanup, missing ABI documentation for the old sysfs
> interfaces is added, and those entries are marked as deprecated
> [01/05 and 03/05]. New ABI documentation is also added for the
> reorganized interfaces. [04/05]
>
> Along with this reorganization, a new sysfs file,
> /sys/kernel/kexec/crash_cma_ranges, is introduced to export crashkernel
> CMA reservation details to user space [05/05]. This helps tools
> determine the total crashkernel reserved memory and warn users that
> capturing user pages while CMA is reserved may cause incomplete or
> unreliable dumps.
Patchset does three unrelated things in remarkably random order.
1: Document existing stuff
Great, thanks, in it goes.
2: export crashkernel CMA reservation to userspace
Well, OK, probably reasonable, didn't look closely.
3: Alter longstanding userspace ABI with deprecation plan
Whoa, tricky, needs careful consideration.
So can we please prepare and consider this material in three separate
patchsets? In the above order, I suggest.
next prev parent reply other threads:[~2025-11-14 23:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 5:14 Sourabh Jain
2025-11-14 5:15 ` [PATCH v4 1/5] Documentation/ABI: add kexec and kdump sysfs interface Sourabh Jain
2025-11-14 5:15 ` [PATCH v4 2/5] kexec: move sysfs entries to /sys/kernel/kexec Sourabh Jain
2025-11-14 5:15 ` [PATCH v4 3/5] Documentation/ABI: mark old kexec sysfs deprecated Sourabh Jain
2025-11-14 5:15 ` [PATCH v4 4/5] kexec: document new kexec and kdump sysfs ABIs Sourabh Jain
2025-11-14 5:15 ` [PATCH v4 5/5] crash: export crashkernel CMA reservation to userspace Sourabh Jain
2025-11-14 23:25 ` Andrew Morton [this message]
2025-11-15 16:09 ` [PATCH v4 0/5] kexec: reorganize sysfs interface and add new kexec sysfs Sourabh Jain
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=20251114152550.ac2dd5e23542f09c62defec7@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=adityag@linux.ibm.com \
--cc=bhe@redhat.com \
--cc=dyoung@redhat.com \
--cc=hbathini@linux.ibm.com \
--cc=jbohac@suse.cz \
--cc=kexec@lists.infradea \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mahesh@linux.ibm.com \
--cc=piliu@redhat.com \
--cc=ritesh.list@gmail.com \
--cc=shivangu@linux.ibm.com \
--cc=sourabhjain@linux.ibm.com \
--cc=sourabhjains@linux.ibm.com \
--cc=vgoyal@redhat.com \
/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®