59 lines · plain
1What: /sys/kernel/fadump/*2Date: Dec 20193Contact: linuxppc-dev@lists.ozlabs.org4Description:5 The /sys/kernel/fadump/* is a collection of FADump sysfs6 file provide information about the configuration status7 of Firmware Assisted Dump (FADump).8 9What: /sys/kernel/fadump/enabled10Date: Dec 201911Contact: linuxppc-dev@lists.ozlabs.org12Description: read only13 Primarily used to identify whether the FADump is enabled in14 the kernel or not.15User: Kdump service16 17What: /sys/kernel/fadump/registered18Date: Dec 201919Contact: linuxppc-dev@lists.ozlabs.org20Description: read/write21 Helps to control the dump collect feature from userspace.22 Setting 1 to this file enables the system to collect the23 dump and 0 to disable it.24User: Kdump service25 26What: /sys/kernel/fadump/release_mem27Date: Dec 201928Contact: linuxppc-dev@lists.ozlabs.org29Description: write only30 This is a special sysfs file and only available when31 the system is booted to capture the vmcore using FADump.32 It is used to release the memory reserved by FADump to33 save the crash dump.34 35What: /sys/kernel/fadump/mem_reserved36Date: Dec 201937Contact: linuxppc-dev@lists.ozlabs.org38Description: read only39 Provide information about the amount of memory reserved by40 FADump to save the crash dump in bytes.41 42What: /sys/kernel/fadump/hotplug_ready43Date: Apr 202444Contact: linuxppc-dev@lists.ozlabs.org45Description: read only46 Kdump udev rule re-registers fadump on memory add/remove events,47 primarily to update the elfcorehdr. This sysfs indicates the48 kdump udev rule that fadump re-registration is not required on49 memory add/remove events because elfcorehdr is now prepared in50 the second/fadump kernel.51User: kexec-tools52 53What: /sys/kernel/fadump/bootargs_append54Date: May 202455Contact: linuxppc-dev@lists.ozlabs.org56Description: read/write57 This is a special sysfs file available to setup additional58 parameters to be passed to capture kernel.59