From: Sourabh Jain <sourabhjain@linux.ibm.com>
To: mpe@ellerman.id.au
Cc: mahesh@linux.vnet.ibm.com, hbathini@linux.ibm.com,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
corbet@lwn.net, linux-doc@vger.kernel.org,
gregkh@linuxfoundation.org,
Sourabh Jain <sourabhjain@linux.ibm.com>
Subject: [PATCH v4 0/6] reorganize and add FADump sysfs files
Date: Fri, 6 Dec 2019 17:54:28 +0530 [thread overview]
Message-ID: <20191206122434.29587-1-sourabhjain@linux.ibm.com> (raw)
Currently, FADump sysfs files are present inside /sys/kernel directory.
But as the number of FADump sysfs file increases it is not a good idea to
push all of them in /sys/kernel directory. It is better to have separate
directory to keep all the FADump sysfs files.
Patch series reorganizes the FADump sysfs files and avail all the existing
FADump sysfs files present inside /sys/kernel into a new directory
/sys/kernel/fadump. The backward compatibility is maintained by adding a
symlink for every sysfs file that has moved to new location. Also a new
FADump sys interface is added to get the amount of memory reserved by FADump
for saving the crash dump.
Changelog:
v1 -> v2:
- Move fadump_release_opalcore sysfs to FADump Kobject instead of
replicating.
- Changed the patch order 1,2,3,4 -> 2,1,3,4 (First add the ABI doc for
exisiting sysfs file then replicate them under FADump kobject).
v2 -> v3:
- Remove the fadump_ prefix from replicated FADump sysfs file names.
v3 -> v4:
- New patch that adds a wrapper function to create symlink with
custom symlink file name.
- Add symlink instead of replicating the FADump sysfs files.
- Move the OPAL core rel
Sourabh Jain (6):
Documentation/ABI: add ABI documentation for /sys/kernel/fadump_*
sysfs: wrap __compat_only_sysfs_link_entry_to_kobj function to change
the symlink name
powerpc/fadump: reorganize /sys/kernel/fadump_* sysfs files
powerpc/powernv: move core and fadump_release_opalcore under new
kobject
Documentation/ABI: mark /sys/kernel/fadump_* sysfs files deprecated
powerpc/fadump: sysfs for fadump memory reservation
.../ABI/obsolete/sysfs-kernel-fadump_enabled | 9 +++
.../obsolete/sysfs-kernel-fadump_registered | 10 +++
.../obsolete/sysfs-kernel-fadump_release_mem | 10 +++
.../sysfs-kernel-fadump_release_opalcore | 9 +++
Documentation/ABI/testing/sysfs-kernel-fadump | 40 +++++++++
.../powerpc/firmware-assisted-dump.rst | 28 +++++--
arch/powerpc/kernel/fadump.c | 81 +++++++++++++++----
arch/powerpc/platforms/powernv/opal-core.c | 31 +++++--
fs/sysfs/group.c | 28 ++++++-
include/linux/sysfs.h | 12 +++
10 files changed, 225 insertions(+), 33 deletions(-)
create mode 100644 Documentation/ABI/obsolete/sysfs-kernel-fadump_enabled
create mode 100644 Documentation/ABI/obsolete/sysfs-kernel-fadump_registered
create mode 100644 Documentation/ABI/obsolete/sysfs-kernel-fadump_release_mem
create mode 100644 Documentation/ABI/removed/sysfs-kernel-fadump_release_opalcore
create mode 100644 Documentation/ABI/testing/sysfs-kernel-fadump
--
2.17.2
next reply other threads:[~2019-12-06 12:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 12:24 Sourabh Jain [this message]
2019-12-06 12:24 ` [PATCH v4 1/6] Documentation/ABI: add ABI documentation for /sys/kernel/fadump_* Sourabh Jain
2019-12-06 12:47 ` Greg KH
2019-12-06 12:24 ` [PATCH v4 2/6] sysfs: wrap __compat_only_sysfs_link_entry_to_kobj function to change the symlink name Sourabh Jain
2019-12-06 12:46 ` Greg KH
2019-12-06 18:27 ` Sourabh Jain
2019-12-06 19:14 ` Greg KH
2019-12-07 3:21 ` Sourabh Jain
2019-12-06 12:24 ` [PATCH v4 3/6] powerpc/fadump: reorganize /sys/kernel/fadump_* sysfs files Sourabh Jain
2019-12-06 12:45 ` Greg KH
2019-12-06 19:13 ` Sourabh Jain
2019-12-06 12:24 ` [PATCH v4 4/6] powerpc/powernv: move core and fadump_release_opalcore under new kobject Sourabh Jain
2019-12-06 12:48 ` Greg KH
2019-12-06 19:16 ` Sourabh Jain
2019-12-06 12:24 ` [PATCH v4 5/6] Documentation/ABI: mark /sys/kernel/fadump_* sysfs files deprecated Sourabh Jain
2019-12-06 12:24 ` [PATCH v4 6/6] powerpc/fadump: sysfs for fadump memory reservation Sourabh Jain
2019-12-06 12:48 ` Greg KH
2019-12-06 19:19 ` 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=20191206122434.29587-1-sourabhjain@linux.ibm.com \
--to=sourabhjain@linux.ibm.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=hbathini@linux.ibm.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mahesh@linux.vnet.ibm.com \
--cc=mpe@ellerman.id.au \
/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®