summaryrefslogtreecommitdiffstats
path: root/src/build/tools
diff options
context:
space:
mode:
authorChristian Geddes <crgeddes@us.ibm.com>2018-04-18 09:36:45 -0500
committerDaniel M. Crowell <dcrowell@us.ibm.com>2018-04-23 20:47:33 -0400
commit812ee5cce1558fc488ce88774fdcf41adad5618b (patch)
treeea392f81721c8fbce080d4004dfdd2bf7bfc3c81 /src/build/tools
parentc5ed4fa654edf1cd2c869677007659578b554119 (diff)
downloadtalos-hostboot-812ee5cce1558fc488ce88774fdcf41adad5618b.tar.gz
talos-hostboot-812ee5cce1558fc488ce88774fdcf41adad5618b.zip
Change all FAPI_INVOKE calls to be FAPI_EXEC in sbe_retry_handler
There are instances where we will call the sbe_retry_handler in the middle of a HWP. This happens when we attempt to use the FIFO path to scom during a HWP and the SBE is dead. This results in the sbe_retry_handler being called which itself will try to run HWPs. If the sbe_retry_handler attempts to call a HWP with FAPI_INVOKE while handling a fail inside a HWP the INVOKE call will get stuck waiting for the fapi mutex to get unlocked which it never will. To get around this we are making all FAPI_INVOKE calls into FAPI_EXEC calls and we are handling the returnCode from FAPI_EXEC locally. Change-Id: I87e54be4ca738c3c327e6519093fb4b6848a542b Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/57401 Reviewed-by: Martin Gloff <mgloff@us.ibm.com> Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com> Tested-by: Jenkins OP Build CI <op-jenkins+hostboot@us.ibm.com> Tested-by: Jenkins OP HW <op-hw-jenkins+hostboot@us.ibm.com> Tested-by: FSP CI Jenkins <fsp-CI-jenkins+hostboot@us.ibm.com> Reviewed-by: Roland Veloz <rveloz@us.ibm.com> Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com>
Diffstat (limited to 'src/build/tools')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud