powerpc: make fadump resilient with memory add/remove events
Subsystems (2)
v10 cover powerpc: make fadump resilient with memory add/remove events
Problem:
========
Due to changes in memory resources caused by either memory hotplug or online/offline events, the elfcorehdr, which describes the cpus and memory of the crashed kernel to the kernel that collects the dump (known as second/fadump kernel), becomes outdated. Consequently, attempting dump collection with an outdated elfcorehdr can lead to failed or inaccurate dump collection.
Memory hotplug or online/offline events is referred as memory add/remove events in reset of the patch series.
Existing solution:
==================
Monitor memory add/remove events in userspace using udev rules, and re-register fadump whenever there are changes in memory resources. This leads to the creation of a new elfcorehdr with updated system memory information.
Challenges with existing solution:
==================================
1. Performing bulk memory add/remove with udev-based fadump re-registration can lead to race conditions and, more importantly, it creates a large wide window during which fadump is inactive until all memory add/remove events are settled.
2. Re-registering fadump for every memory add/remove event is inefficient.
3. Memory for elfcorehdr is allocated based on the memblock regions available during first kernel early boot and it remains fixed thereafter. However, if the elfcorehdr is later recreated with additional memblock regions, its size will increase, potentially leading to memory corruption.
Proposed solution:
==================
Address the aforementioned challenges by shifting the creation of elfcorehdr from the first kernel (also referred as the crashed kernel), where it was created and frequently recreated for every memory add/remove event, to the fadump kernel. As a result, the elfcorehdr only needs to be created once, thus eliminating the necessity to re-register fadump during memory add/remove events.
To know more about elfcorehdr creation in the fadump kernel, refer to the first patch in this series.
The second patch includes a new sysfs interface that tells userspace that fadump re-registration isn't needed for memory add/remove events. note that userspace changes do not need to be in sync with kernel changes; they can roll out independently.
Since there are significant changes in the fadump implementation, the third patch updates the fadump documentation to reflect the changes made in this patch series.
Kernel tree rebased on 6.9.0-rc5 with patch series applied:
===========================================================
https://github.com/sourabhjains/linux/tree/fadump-mem-hotplug-v10
Userspace changes:
==================
To realize this feature, one must update the kdump udev rules to prevent fadump re-registration during memory add/remove events.
On rhel apply the following changes to file/usr/lib/udev/rules.d/98-kexec.rules
-RUN+="/bin/sh -c '/usr/bin/systemctl is-active kdump.service || exit 0; /usr/bin/systemd-run --quiet --no-block /usr/lib/udev/kdump-udev-throttler'"
+# don't re-register fadump if the value of the node
+# /sys/kernel/fadump/hotplug_ready is 1.
+
+RUN+="/bin/sh -c '/usr/bin/systemctl is-active kdump.service || exit 0; ! test -f /sys/kernel/fadump_enabled || cat /sys/kernel/fadump_enabled | grep 0 || ! test -f /sys/kernel/fadump/hotplug_ready || cat /sys/kernel/fadump/hotplug_ready | grep 0 || exit 0; /usr/bin/systemd-run --quiet --no-block /usr/lib/udev/kdump-udev-throttler'"
Changelog:
==========
v10: 23 Apr 2024
- Fix a type cast build error. 1/3
- Rebase it to 6.9-rc5.
v9: 16 Apr 2024
https://lore.kernel.org/all/[email protected]/
- Set the physical address of elfcorehdr to elfcorehdr_addr. 1/3
- Set elfcorehdr_addr to ELFCORE_ADDR_ERR before freeing the elfcorehdr. 1/3
- Mark the populate_elf_pt_load function as __init. 1/3
- Rename a function from process_fadump to fadump_process. 1/3
- Make minor changes to the commit message and a couple of comments in 1/3.
- Update date of introduction of /sys/kernel/fadump/hotplug_ready sysfs. 2/3
- Rebase it to 6.9-rc3.
v8: 16 Feb 2024
https://lore.kernel.org/all/[email protected]/
- Move elfcorehdr_addr and elfcorehdr_size struct attributes from struct fadump_crash_info_header to struct fw_dump.
- Make minor changes in commit message 1/3.
- Rebase it to 6.8-rc4.
v7: 11 Jan 2024
https://lore.kernel.org/all/[email protected]/
- Rebase it to 6.7
v6: 8 Dec 2023
https://lore.kernel.org/all/[email protected]/
- Add size fields for pt_regs and cpumask in the fadump header structure
- Don't process the dump if the size of pt_regs and cpu_mask is not same in the crashed and fadump kernel
- Include an additional check for endianness mismatch when the magic number doesn't match, to print the relevant error message
- Don't process the dump if the fadump header contains an old magic number
- Rebased it to 6.7.0-rc4
v5: 29 Oct 2023
https://lore.kernel.org/all/[email protected]/
- Fix a comment on the first patch
v4: 21 Oct 2023
https://lore.kernel.org/all/[email protected]/
- Fix a build warning about type casting
v3: 9 Oct 2023
https://lore.kernel.org/all/[email protected]/
- Assign physical address of elfcorehdr to fdh->elfcorehdr_addr
- Rename a variable, boot_mem_dest_addr -> boot_mem_dest_offset
v2: 25 Sep 2023
https://lore.kernel.org/all/[email protected]/
- Fixed a few indentation issues reported by the checkpatch script.
- Rebased it to 6.6.0-rc3
v1: 17 Sep 2023
https://lore.kernel.org/all/[email protected]/
Sourabh Jain (3):
powerpc: make fadump resilient with memory add/remove events powerpc/fadump: add hotplug_ready sysfs interface Documentation/powerpc: update fadump implementation details
Documentation/ABI/testing/sysfs-kernel-fadump | 11 + .../arch/powerpc/firmware-assisted-dump.rst | 91 ++--- arch/powerpc/include/asm/fadump-internal.h | 31 +- arch/powerpc/kernel/fadump.c | 375 ++++++++++-------- arch/powerpc/platforms/powernv/opal-fadump.c | 22 +- arch/powerpc/platforms/pseries/rtas-fadump.c | 34 +- 6 files changed, 309 insertions(+), 255 deletions(-)
Signature · 1 line
2.44.0
PATCH v10 1/3 powerpc: make fadump resilient with memory add/remove events
Due to changes in memory resources caused by either memory hotplug or online/offline events, the elfcorehdr, which describes the CPUs and memory of the crashed kernel to the kernel that collects the dump (known as second/fadump kernel), becomes outdated. Consequently, attempting dump collection with an outdated elfcorehdr can lead to failed or inaccurate dump collection.
Memory hotplug or online/offline events is referred as memory add/remove events in reset of the commit message.
The current solution to address the aforementioned issue is as follows:
Monitor memory add/remove events in userspace using udev rules, and re-register fadump whenever there are changes in memory resources. This leads to the creation of a new elfcorehdr with updated system memory information.
There are several notable issues associated with re-registering fadump for every memory add/remove events.
1. Bulk memory add/remove events with udev-based fadump re-registration can lead to race conditions and, more importantly, it creates a wide window during which fadump is inactive until all memory add/remove events are settled.
2. Re-registering fadump for every memory add/remove event is inefficient.
3. The memory for elfcorehdr is allocated based on the memblock regions available during early boot and remains fixed thereafter. However, if elfcorehdr is later recreated with additional memblock regions, its size will increase, potentially leading to memory corruption.
Address the aforementioned challenges by shifting the creation of elfcorehdr from the first kernel (also referred as the crashed kernel), where it was created and frequently recreated for every memory add/remove event, to the fadump kernel. As a result, the elfcorehdr only needs to be created once, thus eliminating the necessity to re-register fadump during memory add/remove events.
At present, the first kernel prepares fadump header and stores it in the fadump reserved area. The fadump header includes the start address of the elfcorehdr, crashing CPU details, and other relevant information. In the event of a crash in the first kernel, the second/fadump boots and accesses the fadump header prepared by the first kernel. It then performs the following steps in a platform-specific function [rtas|opal]_fadump_process:
1. Sanity check for fadump header
2. Update CPU notes in elfcorehdr
Along with the above, update the setup_fadump()/fadump.c to create elfcorehdr and set its address to the global variable elfcorehdr_addr for the vmcore module to process it in the second/fadump kernel.
Section below outlines the information required to create the elfcorehdr and the changes made to make it available to the fadump kernel if it's not already.
To create elfcorehdr, the following crashed kernel information is
required: CPU notes, vmcoreinfo, and memory ranges.
At present, the CPU notes are already prepared in the fadump kernel, so no changes are needed in that regard. The fadump kernel has access to all crashed kernel memory regions, including boot memory regions that are relocated by firmware to fadump reserved areas, so no changes for that either. However, it is necessary to add new members to the fadump header, i.e., the 'fadump_crash_info_header' structure, in order to pass the crashed kernel's vmcoreinfo address and its size to fadump kernel.
In addition to the vmcoreinfo address and size, there are a few other attributes also added to the fadump_crash_info_header structure.
1. version:
It stores the fadump header version, which is currently set to 1. This provides flexibility to update the fadump crash info header in the future without changing the magic number. For each change in the fadump header, the version will be increased. This will help the updated kernel determine how to handle kernel dumps from older kernels. The magic number remains relevant for checking fadump header corruption.
2. pt_regs_sz/cpu_mask_sz:
Store size of pt_regs and cpu_mask structure of first kernel. These attributes are used to prevent dump processing if the sizes of pt_regs or cpu_mask structure differ between the first and fadump kernels.
Note: if either first/crashed kernel or second/fadump kernel do not have the changes introduced here then kernel fail to collect the dump and prints relevant error message on the console.
--- arch/powerpc/include/asm/fadump-internal.h | 31 +- arch/powerpc/kernel/fadump.c | 361 +++++++++++-------- arch/powerpc/platforms/powernv/opal-fadump.c | 22 +- arch/powerpc/platforms/pseries/rtas-fadump.c | 34 +- 4 files changed, 242 insertions(+), 206 deletions(-)
arch/powerpc/include/asm/fadump-internal.h +29 -2
@@ -42,13 +42,38 @@ static inline u64 fadump_str_to_u64(const char *str)#define FADUMP_CPU_UNKNOWN (~((u32)0)) -#define FADUMP_CRASH_INFO_MAGIC fadump_str_to_u64("FADMPINF") +/* +* The introduction of new fields in the fadump crash info header has +* led to a change in the magic key from `FADMPINF` to `FADMPSIG` for +* identifying a kernel crash from an old kernel. +* +* To prevent the need for further changes to the magic number in the +* event of future modifications to the fadump crash info header, a +* version field has been introduced to track the fadump crash info +* header version. +* +* Consider a few points before adding new members to the fadump crash info +* header structure: +* +* - Append new members; avoid adding them in between. +* - Non-primitive members should have a size member as well. +* - For every change in the fadump header, increment the +* fadump header version. This helps the updated kernel decide how to +* handle kernel dumps from older kernels. +*/ +#define FADUMP_CRASH_INFO_MAGIC_OLD fadump_str_to_u64("FADMPINF") +#define FADUMP_CRASH_INFO_MAGIC fadump_str_to_u64("FADMPSIG") +#define FADUMP_HEADER_VERSION 1/* fadump crash info structure */ struct fadump_crash_info_header {u64 magic_number; -u64 elfcorehdr_addr; +u32 version;u32 crashing_cpu; +u64 vmcoreinfo_raddr; +u64 vmcoreinfo_size; +u32 pt_regs_sz; +u32 cpu_mask_sz;struct pt_regs regs;struct cpumask cpu_mask; };
@@ -94,6 +119,8 @@ struct fw_dump {u64 boot_mem_regs_cnt;unsigned long fadumphdr_addr; +u64 elfcorehdr_addr; +u64 elfcorehdr_size;unsigned long cpu_notes_buf_vaddr;unsigned long cpu_notes_buf_size;
arch/powerpc/kernel/fadump.c +205 -156
481 lines not on this page · raw message
arch/powerpc/platforms/powernv/opal-fadump.c +3 -19
@@ -513,8 +513,8 @@ opal_fadump_build_cpu_notes(struct fw_dump *fadump_conf,final_note (note_buf);pr_debug ("Updating elfcore header (%llx) with cpu notes\n" , - fdh->elfcorehdr_addr); -fadump_update_elfcore_header (__va (fdh->elfcorehdr_addr)); + fadump_conf->elfcorehdr_addr); +fadump_update_elfcore_header ((char *)fadump_conf->elfcorehdr_addr);return 0 ; }
@@ -526,12 +526,7 @@ static int __init opal_fadump_process(struct fw_dump *fadump_conf)if (!opal_fdm_active || !fadump_conf->fadumphdr_addr)return rc; -/* Validate the fadump crash info header */ fdh =__va (fadump_conf->fadumphdr_addr); -if (fdh->magic_number !=FADUMP_CRASH_INFO_MAGIC ) { -pr_err ("Crash info header is not valid.\n" ); -return rc; - }#ifdef CONFIG_OPAL_CORE /*
@@ -545,18 +540,7 @@ static int __init opal_fadump_process(struct fw_dump *fadump_conf) kernel_initiated = true;#endif - rc =opal_fadump_build_cpu_notes (fadump_conf, fdh); -if (rc) -return rc; - -/* -* We are done validating dump info and elfcore header is now ready -* to be exported. set elfcorehdr_addr so that vmcore module will -* export the elfcore header through '/proc/vmcore'. -*/ - elfcorehdr_addr = fdh->elfcorehdr_addr; - -return rc; +return opal_fadump_build_cpu_notes (fadump_conf, fdh); } static void opal_fadump_region_show(struct fw_dump *fadump_conf,
arch/powerpc/platforms/pseries/rtas-fadump.c +5 -29
@@ -375,11 +375,8 @@ static int __init rtas_fadump_build_cpu_notes(struct fw_dump *fadump_conf) }final_note (note_buf); -if (fdh) { -pr_debug ("Updating elfcore header (%llx) with cpu notes\n" , - fdh->elfcorehdr_addr); -fadump_update_elfcore_header (__va (fdh->elfcorehdr_addr)); - } +pr_debug ("Updating elfcore header (%llx) with cpu notes\n" , fadump_conf->elfcorehdr_addr); +fadump_update_elfcore_header ((char *)fadump_conf->elfcorehdr_addr);return 0 ; error_out:
@@ -389,14 +386,11 @@ static int __init rtas_fadump_build_cpu_notes(struct fw_dump *fadump_conf) }/* -* Validate and process the dump data stored by firmware before exporting -* it through '/proc/vmcore'. +* Validate and process the dump data stored by the firmware, and update +* the CPU notes of elfcorehdr. */ static int __init rtas_fadump_process (struct fw_dump *fadump_conf) { -struct fadump_crash_info_header *fdh; -int rc =0 ; -if (!fdm_active || !fadump_conf->fadumphdr_addr)return -EINVAL ;
@@ -415,25 +409,7 @@ static int __init rtas_fadump_process(struct fw_dump *fadump_conf)return -EINVAL ; } -/* Validate the fadump crash info header */ - fdh =__va (fadump_conf->fadumphdr_addr); -if (fdh->magic_number !=FADUMP_CRASH_INFO_MAGIC ) { -pr_err ("Crash info header is not valid.\n" ); -return -EINVAL ; - } - - rc =rtas_fadump_build_cpu_notes (fadump_conf); -if (rc) -return rc; - -/* -* We are done validating dump info and elfcore header is now ready -* to be exported. set elfcorehdr_addr so that vmcore module will -* export the elfcore header through '/proc/vmcore'. -*/ - elfcorehdr_addr = fdh->elfcorehdr_addr; - -return 0 ; +return rtas_fadump_build_cpu_notes (fadump_conf); } static void rtas_fadump_region_show(struct fw_dump *fadump_conf,
Signature · 1 line
2.44.0
PATCH v10 2/3 powerpc/fadump: add hotplug_ready sysfs interface
In reply to Sourabh JainThe 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.
--- Documentation/ABI/testing/sysfs-kernel-fadump | 11 +++++++++++ arch/powerpc/kernel/fadump.c | 14 ++++++++++++++ 2 files changed, 25 insertions(+)
Documentation/ABI/testing/sysfs-kernel-fadump +11 -0
@@ -38,3 +38,14 @@ Contact: [email protected] 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: [email protected] +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
arch/powerpc/kernel/fadump.c +14 -0
@@ -1442,6 +1442,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)
@@ -1514,11 +1526,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, ®ister_attr.attr, &mem_reserved_attr.attr, + &hotplug_ready_attr.attr,NULL , };
Signature · 1 line
2.44.0
PATCH v10 3/3 Documentation/powerpc: update fadump implementation details
In reply to Sourabh JainThe patch titled ("powerpc: make fadump resilient with memory add/remove events") has made significant changes to the implementation of fadump, particularly on elfcorehdr creation and fadump crash info header structure. Therefore, updating the fadump implementation documentation to reflect those changes.
Following updates are done to firmware assisted dump documentation:
1. The elfcorehdr is no longer stored after fadump HDR in the reserved dump area. Instead, the second kernel dynamically allocates memory for the elfcorehdr within the address range from 0 to the boot memory size. Therefore, update figures 1 and 2 of Memory Reservation during the first and second kernels to reflect this change.
2. A version field has been added to the fadump header to manage the future changes to fadump crash info header structure without changing the fadump header magic number in the future. Therefore, remove the corresponding TODO from the document.
--- .../arch/powerpc/firmware-assisted-dump.rst | 91 +++++++++---------- 1 file changed, 42 insertions(+), 49 deletions(-)
Documentation/arch/powerpc/firmware-assisted-dump.rst +42 -49
@@ -134,12 +134,12 @@ that are run. If there is dump data, then the memory is held. If there is no waiting dump data, then only the memory required to -hold CPU state, HPTE region, boot memory dump, FADump header and -elfcore header, is usually reserved at an offset greater than boot -memory size (see Fig. 1). This area is *not* released: this region -will be kept permanently reserved, so that it can act as a receptacle -for a copy of the boot memory content in addition to CPU state and -HPTE region, in the case a crash does occur. +hold CPU state, HPTE region, boot memory dump, and FADump header is +usually reserved at an offset greater than boot memory size (see Fig. 1). +This area is *not* released: this region will be kept permanently +reserved, so that it can act as a receptacle for a copy of the boot +memory content in addition to CPU state and HPTE region, in the case +a crash does occur. Since this reserved memory area is used only after the system crash, there is no point in blocking this significant chunk of memory from
@@ -153,22 +153,22 @@ that were present in CMA region:: o Memory Reservation during first kernel - Low memory Top of memory - 0 boot memory size |<--- Reserved dump area --->| | - | | | Permanent Reservation | | - V V | | V - +-----------+-----/ /---+---+----+-------+-----+-----+----+--+ - | | |///|////| DUMP | HDR | ELF |////| | - +-----------+-----/ /---+---+----+-------+-----+-----+----+--+ - | ^ ^ ^ ^ ^ - | | | | | | - \ CPU HPTE / | | - ------------------------------ | | - Boot memory content gets transferred | | - to reserved area by firmware at the | | - time of crash. | | - FADump Header | - (meta area) | + Low memory Top of memory + 0 boot memory size |<------ Reserved dump area ----->| | + | | | Permanent Reservation | | + V V | | V + +-----------+-----/ /---+---+----+-----------+-------+----+-----+ + | | |///|////| DUMP | HDR |////| | + +-----------+-----/ /---+---+----+-----------+-------+----+-----+ + | ^ ^ ^ ^ ^ + | | | | | | + \ CPU HPTE / | | + -------------------------------- | | + Boot memory content gets transferred | | + to reserved area by firmware at the | | + time of crash. | | + FADump Header | + (meta area) | | | Metadata: This area holds a metadata structure whose
@@ -186,13 +186,20 @@ that were present in CMA region:: 0 boot memory size | | |<------------ Crash preserved area ------------>| V V |<--- Reserved dump area --->| | - +-----------+-----/ /---+---+----+-------+-----+-----+----+--+ - | | |///|////| DUMP | HDR | ELF |////| | - +-----------+-----/ /---+---+----+-------+-----+-----+----+--+ - | | - V V - Used by second /proc/vmcore - kernel to boot + +----+---+--+-----/ /---+---+----+-------+-----+-----+-------+ + | |ELF| | |///|////| DUMP | HDR |/////| | + +----+---+--+-----/ /---+---+----+-------+-----+-----+-------+ + | | | | | | + ----- ------------------------------ --------------- + \ | | + \ | | + \ | | + \ | ---------------------------- + \ | / + \ | / + \ | / + /proc/vmcore + +---+ |///| -> Regions (CPU, HPTE & Metadata) marked like this in the above
@@ -200,6 +207,12 @@ that were present in CMA region:: does not have CPU & HPTE regions while Metadata region is not supported on pSeries currently. + +---+ + |ELF| -> elfcorehdr, it is created in second kernel after crash. + +---+ + + Note: Memory from 0 to the boot memory size is used by second kernel + Fig. 2
@@ -353,26 +366,6 @@ TODO: - Need to come up with the better approach to find out more accurate boot memory size that is required for a kernel to boot successfully when booted with restricted memory. - - The FADump implementation introduces a FADump crash info structure - in the scratch area before the ELF core header. The idea of introducing - this structure is to pass some important crash info data to the second - kernel which will help second kernel to populate ELF core header with - correct data before it gets exported through /proc/vmcore. The current - design implementation does not address a possibility of introducing - additional fields (in future) to this structure without affecting - compatibility. Need to come up with the better approach to address this. - - The possible approaches are: - - 1. Introduce version field for version tracking, bump up the version - whenever a new field is added to the structure in future. The version - field can be used to find out what fields are valid for the current - version of the structure. - 2. Reserve the area of predefined size (say PAGE_SIZE) for this - structure and have unused area as reserved (initialized to zero) - for future field additions. - - The advantage of approach 1 over 2 is we don't need to reserve extra space. Author: Mahesh Salgaonkar <[email protected]>
Signature · 1 line
2.44.0
Michael Ellerman
AppliedQuoted 10 lines · Sourabh Jain
Problem:
========
Due to changes in memory resources caused by either memory hotplug or online/offline events, the elfcorehdr, which describes the cpus and memory of the crashed kernel to the kernel that collects the dump (known as second/fadump kernel), becomes outdated. Consequently, attempting dump collection with an outdated elfcorehdr can lead to failed or inaccurate dump collection.[...]
Applied to powerpc/next.
[1/3] powerpc: make fadump resilient with memory add/remove events
https://git.kernel.org/powerpc/c/c6c5b14dac0d1bd0da8b4d1d3b77f18eb9085fcb [2/3] powerpc/fadump: add hotplug_ready sysfs interface https://git.kernel.org/powerpc/c/bc446c5acabadeb38b61b565535401c5dfdd1214 [3/3] Documentation/powerpc: update fadump implementation details https://git.kernel.org/powerpc/c/57e6700145c5d1f49c52137e9163f73ec5441256
cheers