diff options
| author | Vasant Hegde <hegdevasant@linux.vnet.ibm.com> | 2020-08-27 10:55:25 +0530 |
|---|---|---|
| committer | Vasant Hegde <hegdevasant@linux.vnet.ibm.com> | 2020-09-09 20:03:00 +0530 |
| commit | f618d584e5d4c2fb87078aa7b98441b0a11b7807 (patch) | |
| tree | 53880e4cdf562657daa16798d7de9fa41f42daa8 | |
| parent | 2c309d71e0b762b19163bb022ec1faba2ea122aa (diff) | |
| download | skiboot-f618d584e5d4c2fb87078aa7b98441b0a11b7807.zip skiboot-f618d584e5d4c2fb87078aa7b98441b0a11b7807.tar.gz skiboot-f618d584e5d4c2fb87078aa7b98441b0a11b7807.tar.bz2 | |
fsp/dump: Handle non-MPIPL scenario
[ Upstream commit 0ad0ab3e24a322b79bec8451bc21e9bdd40a6657 ]
If MPIPL is not enabled then we will not create `/ibm,opal/dump` node
and we should continue to parse/retrieve SYSDUMP. I missed this scenario
when I fixed similar issue last time :-(
Fixes: 92b7968 (fsp: Skip sysdump retrieval only in MPIPL boot)
Signed-off-by: Vasant Hegde <hegdevasant@linux.vnet.ibm.com>
Signed-off-by: Oliver O'Halloran <oohall@gmail.com>
Signed-off-by: Vasant Hegde <hegdevasant@linux.vnet.ibm.com>
| -rw-r--r-- | hw/fsp/fsp-dump.c | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/hw/fsp/fsp-dump.c b/hw/fsp/fsp-dump.c index 3ea353a..96cb45e 100644 --- a/hw/fsp/fsp-dump.c +++ b/hw/fsp/fsp-dump.c @@ -830,10 +830,10 @@ static void check_ipl_sys_dump(void) if (!opal_node) return; dump_node = dt_find_by_path(opal_node, "dump"); - if (!dump_node) - return; - if (dt_find_property(dump_node, "mpipl-boot")) - return; + if (dump_node) { + if (dt_find_property(dump_node, "mpipl-boot")) + return; + } } dump_node = dt_find_by_path(dt_root, "ipl-params/platform-dump"); |