aboutsummaryrefslogtreecommitdiff
path: root/LICENCE
diff options
context:
space:
mode:
authorVasant Hegde <hegdevasant@linux.vnet.ibm.com>2020-06-17 12:46:10 +0530
committerOliver O'Halloran <oohall@gmail.com>2020-06-30 12:07:23 +1000
commitedc936afb6e34a9182244c7f4e9f117afd52fb6e (patch)
tree9041088cc841eb22db1bf99364aa30e2bfbc4303 /LICENCE
parent9f5374b46aab4a2980d5bf745d79fa9d7bb609e1 (diff)
downloadskiboot-edc936afb6e34a9182244c7f4e9f117afd52fb6e.zip
skiboot-edc936afb6e34a9182244c7f4e9f117afd52fb6e.tar.gz
skiboot-edc936afb6e34a9182244c7f4e9f117afd52fb6e.tar.bz2
mpipl: Move opal_mpipl_save_crashing_pir() call to platform specific code
Commit 34664746 moved opal_mpipl_save_crashing_pir() function call from platform specific code to generic assert() path. I completely missed to take care of all terminate path :-( This resulted in breaking `opalcore` on Linux kernel initiated MPIPL. As : - Linux initiated MPIPL calls platform termination function directly - ELF core format needs crashing CPU details to generate proper code Hence I think it makes sense to move this back to platform specific terminate handler code. Today we have two ways to trigger MPIPL based on service processor. - On BMC system we call SBE S0 interrupt - On FSP system we call `attn` instruction In future if we add new ways to trigger MPIPL then we have to add platform specific support code anyway. That way its fine to move this to platform sepcific code. One alternative is to make this call in all code path before making platform.terminate call... which makes it more complicated than above approach. Signed-off-by: Vasant Hegde <hegdevasant@linux.vnet.ibm.com> Signed-off-by: Oliver O'Halloran <oohall@gmail.com>
Diffstat (limited to 'LICENCE')
0 files changed, 0 insertions, 0 deletions