powerpc/fadump: add hotplug_ready sysfs interface
authorSourabh Jain <sourabhjain@linux.ibm.com>
Mon, 22 Apr 2024 19:59:31 +0000 (01:29 +0530)
committerMichael Ellerman <mpe@ellerman.id.au>
Mon, 29 Apr 2024 13:51:15 +0000 (23:51 +1000)
The elfcorehdr describes the CPUs and memory of the crashed kernel to
the kernel that captures the dump, known as the second or fadump kernel.
The elfcorehdr needs to be updated if the system's memory changes due to
memory hotplug or online/offline events.

Currently, memory hotplug events are monitored in userspace by udev
rules, and fadump is re-registered, which recreates the elfcorehdr with
the latest available memory in the system.

However, the previous patch ("powerpc: make fadump resilient with memory
add/remove events") moved the creation of elfcorehdr to the second or
fadump kernel. This eliminates the need to regenerate the elfcorehdr
during memory hotplug or online/offline events.

Create a sysfs entry at /sys/kernel/fadump/hotplug_ready to let
userspace know that fadump re-registration is not required for memory
add/remove events.

Signed-off-by: Sourabh Jain <sourabhjain@linux.ibm.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Link: https://msgid.link/20240422195932.1583833-3-sourabhjain@linux.ibm.com
Documentation/ABI/testing/sysfs-kernel-fadump
arch/powerpc/kernel/fadump.c

index 8f7a64a81783a53b4d696f79df0d5ab72cee8475..c586054657d63dc992c1d68125a1cdadaec8cf83 100644 (file)
@@ -38,3 +38,14 @@ Contact:     linuxppc-dev@lists.ozlabs.org
 Description:   read only
                Provide information about the amount of memory reserved by
                FADump to save the crash dump in bytes.
+
+What:          /sys/kernel/fadump/hotplug_ready
+Date:          Apr 2024
+Contact:       linuxppc-dev@lists.ozlabs.org
+Description:   read only
+               Kdump udev rule re-registers fadump on memory add/remove events,
+               primarily to update the elfcorehdr. This sysfs indicates the
+               kdump udev rule that fadump re-registration is not required on
+               memory add/remove events because elfcorehdr is now prepared in
+               the second/fadump kernel.
+User:          kexec-tools
index a020597c065a2f1a1322cde59f35c0ee1817be33..2de7379d0f300d606d5da64c58ec896a9940e0cd 100644 (file)
@@ -1426,6 +1426,18 @@ static ssize_t enabled_show(struct kobject *kobj,
        return sprintf(buf, "%d\n", fw_dump.fadump_enabled);
 }
 
+/*
+ * /sys/kernel/fadump/hotplug_ready sysfs node returns 1, which inidcates
+ * to usersapce that fadump re-registration is not required on memory
+ * hotplug events.
+ */
+static ssize_t hotplug_ready_show(struct kobject *kobj,
+                                     struct kobj_attribute *attr,
+                                     char *buf)
+{
+       return sprintf(buf, "%d\n", 1);
+}
+
 static ssize_t mem_reserved_show(struct kobject *kobj,
                                 struct kobj_attribute *attr,
                                 char *buf)
@@ -1498,11 +1510,13 @@ static struct kobj_attribute release_attr = __ATTR_WO(release_mem);
 static struct kobj_attribute enable_attr = __ATTR_RO(enabled);
 static struct kobj_attribute register_attr = __ATTR_RW(registered);
 static struct kobj_attribute mem_reserved_attr = __ATTR_RO(mem_reserved);
+static struct kobj_attribute hotplug_ready_attr = __ATTR_RO(hotplug_ready);
 
 static struct attribute *fadump_attrs[] = {
        &enable_attr.attr,
        &register_attr.attr,
        &mem_reserved_attr.attr,
+       &hotplug_ready_attr.attr,
        NULL,
 };