diff options
| author |   Hari Bathini <hbathini@linux.ibm.com> | 2022-02-01 16:23:05 +0530 |
|---|---|---|
| committer |   Michael Ellerman <mpe@ellerman.id.au> | 2022-03-01 23:41:00 +1100 |
| commit | 607451ce0aa9bdff590db4d087173edba6d7a29d (patch) | |
| tree | 489d9d79a02a728379b56283844d0dfbdcd0c139 /arch/powerpc/mm/numa.c | |
| parent | selftests/powerpc/pmu: Add interface test for mmcra register fields (diff) | |
| download | linux-dev-607451ce0aa9bdff590db4d087173edba6d7a29d.tar.xz linux-dev-607451ce0aa9bdff590db4d087173edba6d7a29d.zip | |
powerpc/fadump: register for fadump as early as possible
Crash recovery (fadump) is setup in the userspace by some service. This
service rebuilds initrd with dump capture capability, if it is not
already dump capture capable before proceeding to register for firmware
assisted dump (echo 1 > /sys/kernel/fadump/registered). But arming the
kernel with crash recovery support does not have to wait for userspace
configuration. So, register for fadump while setting it up itself. This
can at worst lead to a scenario, where /proc/vmcore is ready afer crash
but the initrd does not know how/where to offload it, which is always
better than not having a /proc/vmcore at all due to incomplete
configuration in the userspace at the time of crash.
Commit 0823c68b054b ("powerpc/fadump: re-register firmware-assisted dump
if already registered") ensures this change does not break userspace.
Signed-off-by: Hari Bathini <hbathini@linux.ibm.com>
[mpe: Reword comment]
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Link: https://lore.kernel.org/r/20220201105305.155511-1-hbathini@linux.ibm.com
Diffstat (limited to 'arch/powerpc/mm/numa.c')
0 files changed, 0 insertions, 0 deletions