summaryrefslogtreecommitdiffstats
path: root/src/usr/sbeio
Commit message (Collapse)AuthorAgeFilesLines
* Deconfig record can't get added to vitalAttn elog on FSPChristian Geddes2018-05-141-3/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | On FSP system we should never try to call vitalAttnHandler because the fir bits that trigger this code should be masked. However we have seen issues where for whatever reason the firs get unmasked. If we happen to fall into this code on a FSP system we want to make sure that no deconfigure records get added to the error logs that get generated. If deconfig records get added it can collide with the flow that hwsv is doing to attempt to recover the SBE. Also in this commit we removed the TODO for disabling the OCC if the SBE dies. We have decided that it is no longer necessary to disable the OCC if the SBE dies. See story for more information. Change-Id: Ib75dc34a122a37853047af67ec8858dbca11e4a2 CQ: SW427127 RTC: 180244 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/58226 Reviewed-by: Martin Gloff <mgloff@us.ibm.com> Reviewed-by: Brian E. Bakke <bbakke@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: 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> Tested-by: Jenkins OP HW <op-hw-jenkins+hostboot@us.ibm.com>
* Add error log for sbe poweron fails and clean up errlog commitsChristian Geddes2018-05-071-9/+42
| | | | | | | | | | | | | | | | | | | | | | This commit introduces a new error log that will get displayed when a slave SBE fails to reach runtime after the intial start_cbs. Before adding this there was no notification letting the user know that Hostboot failed to boot the slave sbe and that it gave control to the FSP so hwsv can figure out what to do next. In addition to this new error log this commit also updates other errlCommit func calls in the sbe_retry_handler to ensure we are using SBEIO as the component id for these error logs. Change-Id: I73854f753a6186958d55909e8e37a605c1ad57c9 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/58049 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: Martin Gloff <mgloff@us.ibm.com> Reviewed-by: Brian E. Bakke <bbakke@us.ibm.com> Reviewed-by: Roland Veloz <rveloz@us.ibm.com> Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com>
* Fixed the SBE FFDC parsing issue of mssing traces and attributesRoland Veloz2018-05-022-85/+114
| | | | | | | | | | | | | | | | | | | | | Not exactly sure why the code was not printing out the wanted traces and attribute data, but apparently the files that contains the code for the SBEIO FFDC parser, file sbeIoErrlUd.H and file sbeIoFfdcType.H, are a copy of what is in the FSP repo, files sbeUserDataParser.C and sbeFFDCType.H. The HB files were out of sync with FSP files. Once I updated the HB files, literally just copied the contents of the FSP files into the HB files, the traces and attribute data appeared. Turns out it was just a syncing issue. Change-Id: I84e55d0cd0ed81034bbf774af049f5b486278f5f CQ:SW415480 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/54057 Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com> Tested-by: FSP CI Jenkins <fsp-CI-jenkins+hostboot@us.ibm.com> Reviewed-by: ILYA SMIRNOV <ismirno@us.ibm.com> Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com> Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/58001 Tested-by: Jenkins OP Build CI <op-jenkins+hostboot@us.ibm.com> Tested-by: Jenkins OP HW <op-hw-jenkins+hostboot@us.ibm.com>
* Change all FAPI_INVOKE calls to be FAPI_EXEC in sbe_retry_handlerChristian Geddes2018-04-231-11/+53
| | | | | | | | | | | | | | | | | | | | | | 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>
* Add recovery summary traces for sbeAttemptRecovery for FSP runtimeChristian Geddes2018-04-181-0/+4
| | | | | | | | | | | | | | | | | | Previously you had to look at other traces, or decipher to binary trace to determine if the sbe was recovered or not, this commit adds clear traces after the recover effort is done to tell whether it was successful or not. Change-Id: I17ce4de2f7e1168409758ca0ef1a5eaa044d6728 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/57146 CI-Ready: Christian R. Geddes <crgeddes@us.ibm.com> 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>
* Ensure that we only attempt to recover from vital attn on BMC systemsChristian Geddes2018-04-181-0/+7
| | | | | | | | | | | | | | | | | | | | On an FSP system PRD should never get triggered on an SBE vital attn. However if for any reason PRD attempts to handle a vital attn on an FSP system HB should not actually perform any recovery and we should just return an error back to PRD signaling that we could not recover. PRD should stop mask off the error after the handler returns with an error saying we could not recover. Change-Id: If1666bd028da9a94bed34d79da34f6264beb0fbf Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/57176 CI-Ready: Christian R. Geddes <crgeddes@us.ibm.com> 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: William G. Hoffa <wghoffa@us.ibm.com>
* Change sbe restart fail hwCallouts from GARDs to DECONFIGChristian Geddes2018-04-161-9/+9
| | | | | | | | | | | | | | | | | | During the hreset and start_cbs hwps if we get an error (likely scom or cfam error) then we want to callout the processor. Previously we were GARDing out the processor if this occurred. It was pointed out this might be a little harsh so instead we are going to deconfigure the processor Change-Id: Id5bfe0af392a4863ef2d225777bc17f3c308340e Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/56960 Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com> 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: William G. Hoffa <wghoffa@us.ibm.com>
* Improve linking of PLIDs for sbe_retry_handlerChristian Geddes2018-04-131-60/+35
| | | | | | | | | | | | | | | | | | Previously if a PLID was passed to the ctor of the sbe_retry_handler we would link all errors logs created during the process of recovering the SBE with this PLID. But if no PLID was passed then we would not link the logs. This commit changes it so if no PLID is passed to the ctor then the first log created in the recovery process will become the PLID that all logs after will be set to. Change-Id: I93ef3a48b4cc1d7df3237d7ba3dfefba21d5fb6b Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/56885 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: Daniel M. Crowell <dcrowell@us.ibm.com>
* Revert "Clear perv scrach register prior to triggering HRESET"Christian R. Geddes2018-04-101-48/+6
| | | | | | | | | | This reverts commit 4f32915aa1240d07bb2671010f95695ba5f306c3. Change-Id: Ie51fd274d018df63aef6f725bf57c7b1f7f59265 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/57026 CI-Ready: Christian R. Geddes <crgeddes@us.ibm.com> Reviewed-by: Christian R. Geddes <crgeddes@us.ibm.com> Tested-by: Christian R. Geddes <crgeddes@us.ibm.com>
* Clear perv scrach register prior to triggering HRESETChristian Geddes2018-04-101-6/+48
| | | | | | | | | | | | | | | | | | | | | | Before we initiate an HRESET we need to make sure that the perv scratch register that the SBE looks at during boot are all zeros. When these registers are zeros the SBE will ignore them and pull values from its own image. We need to do this because Hostboot will repurpose these registers after the SBE boots the first time so the data in the registers is no longer valid. It is okay for the SBE to pull the values from it's own image because during the IPL hostboot customized the SBE image with the correct values. Change-Id: I8b434d04cde3c384e35a3089a349a1d121b6b1dc RTC: 180242 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/56959 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> CI-Ready: Christian R. Geddes <crgeddes@us.ibm.com> Tested-by: Jenkins OP HW <op-hw-jenkins+hostboot@us.ibm.com> Reviewed-by: Roland Veloz <rveloz@us.ibm.com> Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com>
* Enable OpenPower SBE Vital Attention handlerChristian Geddes2018-04-105-28/+132
| | | | | | | | | | | | | | | | | | | | | | | | If PRD notices that a sbe vital attention is set (TP_LFIR 26) then it will call hostboot code to attempt to recover the SBE. If this occurs during IPL time then hostboot will not be able to recover the SBE and we will deconfigure the processor. If this occurs during runtime HBRT will attempt to run the retry_handler. This will result in us calling hreset on the SBE that failed. If we were able to recover the SBE then no error will be returned. If we are unable to recover the SBE then we will return an error with a deconfig record. Change-Id: I3da6ec932ef8e59f7b2a184621a47e88d465e0c5 RTC: 167191 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/56821 CI-Ready: Daniel M. Crowell <dcrowell@us.ibm.com> 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>
* Hook up FSP runtime support for sbe_retry_handler (hreset path)Christian Geddes2018-04-094-52/+39
| | | | | | | | | | | | | | | | | | | | | | | | | | | In the sbe_retry_handler code we have two methods we can use to restart the sbe. They are restarting the cfam boot sequence (start_cbs HWP) and performing a hw reset on the PPE (hreset HWP). We use start_cbs if there are issues with initial power on of the slave proc's SBE because we will not lose any state info (fabric isn't up yet). During runtime we will want to use the hreset HWP to recover the SBE. Hreset is handy because it will not force a reboot of the entire proc chip, so the fabric can stay up while we reset the PPE in the SBE. This commit implements the code path for the hreset HWP in the sbe_retry_handler. In addition this commit enables calls to the sbe_retry_handler in rt_fwnotify's sbeAttemptRecovery function which handles PHYP requests to recover the SBE. (Also some small typos in related code fixed) Change-Id: I8f85c38a09e8d5ab80b2809e5665c77a54e35bc4 CQ: SW415675 RTC: 180242 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/56276 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> Reviewed-by: Roland Veloz <rveloz@us.ibm.com> Tested-by: FSP CI Jenkins <fsp-CI-jenkins+hostboot@us.ibm.com> Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com>
* sbe_retry_handler refactorChristian Geddes2018-04-068-688/+844
| | | | | | | | | | | | | | | | | | | Previously the sbe_retry_handler had logic and wording that assumed that it was being used to tell if the slave sbe booted or not. However this code has many more use cases then that. Also there was some indirect recursion that made the code hard to follow. With this refactor the code should be easier to follow and the vocabulary used should be more generic. Change-Id: If6520197b3dd561857e336ed89d9356c1f2601d6 CQ: SW416106 RTC: 167191 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/55896 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> Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com> Tested-by: Daniel M. Crowell <dcrowell@us.ibm.com>
* Inform OPAL of the state of the SBE after an attempt to restartRoland Veloz2018-03-223-2/+124
| | | | | | | | | | | | | | | | | Inform OPAL of the state of the SBE after an attempt to restart, either it is disabled or enabled after retry, along with the processor ID of the SBE. Change-Id: I66a58e866c602c53f41f7cdfbd798f613d3b4dab RTC:180245 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/54813 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: Martin Gloff <mgloff@us.ibm.com> Reviewed-by: Christian R. Geddes <crgeddes@us.ibm.com> Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com>
* Add proc huid to PSU traceDan Crowell2018-03-161-2/+3
| | | | | | | | | | | | | Change-Id: I5173489e04c83ce85a8c8942f92b1ddab585fda8 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/55274 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: Matt Derksen <mderkse1@us.ibm.com> Reviewed-by: Martin Gloff <mgloff@us.ibm.com> Reviewed-by: Christian R. Geddes <crgeddes@us.ibm.com> Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com>
* Adding visible error once we know that the SBE is erroringElizabeth Liner2018-02-271-2/+29
| | | | | | | | | | | | | | | | | | There is a path of the sbe_retry_handler that is missing a visible error (Once we realize that there is an issue with the SBE, and we're attempting a boot). This commit adds in that change Change-Id: Ia613d0b5210aec7bfa923f565d3f57192e585361 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/53774 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> CI-Ready: Christian R. Geddes <crgeddes@us.ibm.com> Reviewed-by: Christian R. Geddes <crgeddes@us.ibm.com> Reviewed-by: Martin Gloff <mgloff@us.ibm.com> Reviewed-by: William G. Hoffa <wghoffa@us.ibm.com>
* Remove if that was catching SBE chipop err logs and forcing rebootChristian Geddes2018-02-212-67/+0
| | | | | | | | | | | | | | | | | | | Before Hostboot had the ability to parse SBE FFDC, we would perform a special shutdown that would request the FSP to parse the SBE FFDC in the event of a SBE chip-op (PSU or FIFO) failure. Now that hostboot can do this we do not need to go down this path in this case. The only time we should do this is if the SbeRetryHandler has decided that this is required. CQ: SW417255 Change-Id: I8f52d52294d84c9e10faf7d8bc500808463aa57f Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/54063 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> Reviewed-by: Nicholas E. Bofferding <bofferdn@us.ibm.com> Tested-by: FSP CI Jenkins <fsp-CI-jenkins+hostboot@us.ibm.com> Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com>
* Increase SBE FIFO delay timeoutDean Sanner2018-02-161-1/+1
| | | | | | | | | | | | | | | Architected value for worst case is 90 sec. Code was setting it to 10ms, which was occasionally causing timeouts on long running operations (MPIPL continue). Change-Id: I51b05ad4daa56901402a34dee4a24f73bfd479f2 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/53573 Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com> Tested-by: Jenkins OP Build CI <op-jenkins+hostboot@us.ibm.com> Tested-by: FSP CI Jenkins <fsp-CI-jenkins+hostboot@us.ibm.com> Tested-by: Jenkins OP HW <op-hw-jenkins+hostboot@us.ibm.com> Reviewed-by: Prachi Gupta <pragupta@us.ibm.com> Reviewed-by: William G. Hoffa <wghoffa@us.ibm.com>
* Send additional FSP progress messages during long isteps (e.g. memdiags)Rick Ward2018-02-151-36/+4
| | | | | | | | | | | | | | | | | | | Updated sendProgressCode() so that it would only output trace or console messages once per step/substep. Replaced most calls to IPMIWATCHDOG::resetWatchDogTimer() with calls to sendProgressCode() which calls resetWatchDogTimer() if communicating with a BMC, or updates the FSP with its progress on FSP-based systems. Change-Id: I29beb7ce5cdae467d26a0b2c5fee9e3cc4629161 RTC: 169682 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/53995 Reviewed-by: William G. Hoffa <wghoffa@us.ibm.com> Reviewed-by: Prachi Gupta <pragupta@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: Daniel M. Crowell <dcrowell@us.ibm.com>
* Moving Sbe Retry Handler work to common file for runtimeElizabeth Liner2018-02-155-10/+39
| | | | | | | | | | | | | | | | We want to move the sbe_retry_handler.C and other files associated with it to a common directory and makefile. Change-Id: Ifc725709d23d9eec75d2f91b2be73728c91a8d86 RTC:180241 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/53591 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: Martin Gloff <mgloff@us.ibm.com> Reviewed-by: Roland Veloz <rveloz@us.ibm.com> Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com>
* Enable sbeio runtime testcasesBill Hoffa2018-02-153-13/+13
| | | | | | | | | | | | | | Change-Id: Id5d8ef64606cd808cc05e4ec4f0a317773317b67 RTC: 178802 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/54065 Reviewed-by: Matt Derksen <mderkse1@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: Corey V. Swenson <cswenson@us.ibm.com> Reviewed-by: Prachi Gupta <pragupta@us.ibm.com> Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com>
* Enable fsidd testcases for Cumulus modelBill Hoffa2018-02-151-1/+1
| | | | | | | | | | | | | Change-Id: I3ad1335d734ec04e7cc68833662bf228302b838f RTC:178802 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/54037 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: Corey V. Swenson <cswenson@us.ibm.com> Reviewed-by: Prachi Gupta <pragupta@us.ibm.com> Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com>
* Increase poll wait time for SBE PSU operationsDan Crowell2018-02-151-2/+2
| | | | | | | | | | Adding an explicit sleep versus relying on a context switch to determine when PSU operations to the SBE have timed out. Change-Id: I411b45f3ce793eb60e7defe37cf4273abd5d066a Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/54048 Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com> Tested-by: Daniel M. Crowell <dcrowell@us.ibm.com>
* Fixing SBE PSU error messagesElizabeth Liner2018-02-141-8/+59
| | | | | | | | | | | | | | | | When we added support for SBE rebooting, an error was incorrectly removed - the error when there is a correct PSU timeout that is not associated with the SBE. This commit adds that error back in. Change-Id: Ie289f5ff5312d0b1415a98531fd4a8b94cef37ae Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/52844 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: William G. Hoffa <wghoffa@us.ibm.com> Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com>
* Initialize SBE message communication on HBRT startMatt Derksen2018-02-071-79/+88
| | | | | | | | | | | | | | | | | | | Need to clear first 2 bits in CFAM register 0x283B. This basically resets our SBE communication stream just incase HBRT restarts after processing SBE interrupt. Clearing these bits tells the sender to resend the command. Change-Id: I1a1c5b80cc99414649d38c06b93428c87299f242 RTC:186334 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/53225 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> Reviewed-by: Brian E. Bakke <bbakke@us.ibm.com> Reviewed-by: Roland Veloz <rveloz@us.ibm.com> Tested-by: FSP CI Jenkins <fsp-CI-jenkins+hostboot@us.ibm.com> Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com>
* Always have secureModeDisable bit set to 0 in sbe_retry_handlerChristian Geddes2018-02-041-1/+1
| | | | | | | | | | | | | | | | | After talking with the HWP writers for the sbe_extract_rc HWP they told us we should always act like the secureModeDisable bit is false. The only reason that option is there is for lab use and we shouldnt ever use it. This commit makes that bit always 0 Change-Id: Id781df3a95ffdf5ec82624aebe6830f17d7dcf2b Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/52861 Reviewed-by: Elizabeth K. Liner <eliner@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>
* HB supports - Use ADU chipops to switch fabric configurationThi Tran2018-02-032-85/+224
| | | | | | | | | | | | | Change-Id: I090cdac654d9c6efbe30748713687c6e36ff914d RTC:177597 CQ:SW413432 Backport: release-fips910 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/52878 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: Daniel M. Crowell <dcrowell@us.ibm.com>
* Save away SBE FFDC and COMM area address in corresponding attrsChristian Geddes2018-02-011-2/+8
| | | | | | | | | | | | | | | | | | | | | We set the SBE's FFDC and COMM area addresses in at least 2 points of the IPL. The first time we do (PSU chip op) we were sending the addr down to the SBE but we were not storing it in the platform attributes SBE_FFDC_ADDR and SBE_COMM_ADDR. This commit adds some code that will save off these values. Functionally this was correct before, but it might have been confusing to debug a problem when the SBE's FFDC area wasn't matching what attribute told us Change-Id: I5cd9d63bf8be26093a24f28ff82a05ac8321a338 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/52594 Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com> Reviewed-by: Martin Gloff <mgloff@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: Matt Derksen <mderkse1@us.ibm.com> Reviewed-by: Roland Veloz <rveloz@us.ibm.com> Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com>
* Fixing timeout error in PSU code - removing hangElizabeth Liner2018-01-301-2/+2
| | | | | | | | | | | | | | | | | There was an issue in the PSU SBE code where we were hanging, and subsequently failing. This changes the elapsed time counter to increment more quickly. Change-Id: I3c4c4905b8bad81c5dcca1e7d7bd5935a9e671a6 CQ:SW410105 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/52934 Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com> Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com> Reviewed-by: Martin Gloff <mgloff@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: William G. Hoffa <wghoffa@us.ibm.com>
* Add sbe_retry_handler to FIFO fail pathChristian Geddes2018-01-302-6/+62
| | | | | | | | | | | | | | | | | | | | In the event of a FIFO communication failure w/ SBE, hostboot wants to run the sbe_retry_handler in order to collect as much FFDC as possible. We were missing support for this before this commit. This commit also adds support for the sbe_retry_handler to use the Secure Debug Bit and the unsecure mode bit for the p9_extract_rc hwp. Change-Id: I171abd89ccf4e78ffcc7c1190b58af3b11846362 CQ:SW395356 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/52702 Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com> Reviewed-by: Martin Gloff <mgloff@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> Reviewed-by: Roland Veloz <rveloz@us.ibm.com> Reviewed-by: Elizabeth K. Liner <eliner@us.ibm.com> Tested-by: FSP CI Jenkins <fsp-CI-jenkins+hostboot@us.ibm.com> Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com>
* Extract error info from PIBMEM array save-offSoma BhanuTej2018-01-242-4/+22
| | | | | | | | | | | | | | | | | | Change-Id: Ib7f66c6214bf0825ba38ffa1c7ecd81f5ae20e53 CQ: SW414284 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/49219 Tested-by: FSP CI Jenkins <fsp-CI-jenkins+hostboot@us.ibm.com> Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com> Tested-by: HWSV CI <hwsv-ci+hostboot@us.ibm.com> Tested-by: Hostboot CI <hostboot-ci+hostboot@us.ibm.com> Reviewed-by: Anusha Reddy Rangareddygari <anusrang@in.ibm.com> Reviewed-by: RAJA DAS <rajadas2@in.ibm.com> Reviewed-by: SRINIVAS V. POLISETTY <srinivan@in.ibm.com> Reviewed-by: Jennifer A. Stofer <stofer@us.ibm.com> Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/49224 Tested-by: Jenkins OP Build CI <op-jenkins+hostboot@us.ibm.com> Tested-by: Jenkins OP HW <op-hw-jenkins+hostboot@us.ibm.com> Reviewed-by: Christian R. Geddes <crgeddes@us.ibm.com>
* Move closing all unsecure memory regions to 21.3Stephen Cprek2018-01-222-1/+17
| | | | | | | | | | | | | | | | | | | | Current windows that are left open at end of IPL - SBE FFDC - CPU Controls SP ATTN area - 0-64MB for SP ATTN Change-Id: I887fc63bcc70f2351530741bd251db12732a5948 RTC:168745 Backport:release-fips910 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/52045 Reviewed-by: Michael Baiocchi <mbaiocch@us.ibm.com> Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com> Tested-by: FSP CI Jenkins <fsp-CI-jenkins+hostboot@us.ibm.com> Tested-by: Jenkins OP Build CI <op-jenkins+hostboot@us.ibm.com> Reviewed-by: Nicholas E. Bofferding <bofferdn@us.ibm.com> Reviewed-by: Marshall J. Wilks <mjwilks@us.ibm.com> Tested-by: Jenkins OP HW <op-hw-jenkins+hostboot@us.ibm.com> Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com>
* Propagate PLID from caller to any new errors; GARD target on retry failsRoland Veloz2018-01-181-5/+125
| | | | | | | | | | | | | | | | | For any new errors, if caller has provided a PLID, that PLID is to replace the new error's PLID. Also gard out the target associated with the SBE if the SBE retry fails. Change-Id: Ic0bf1a0233c1cda8f91dd0ef093bd6c9e31574bd RTC:184891 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/51904 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: Christian R. Geddes <crgeddes@us.ibm.com> Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com>
* Make the MemRegionMgr class target awareStephen Cprek2018-01-172-48/+165
| | | | | | | | | | | | | | | | | Creates a map of target,region map lists to allow the opening of the same regions against different targets Change-Id: Ieb2235765da99b25c018a5e9546ac2f8ca252a39 CQ:SW412793 Backport:release-fips910 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/51923 Reviewed-by: Nicholas E. Bofferding <bofferdn@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: Michael Baiocchi <mbaiocch@us.ibm.com> Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com>
* Adding advanced restart logic after detecting vital attentionsElizabeth Liner2017-12-222-12/+30
| | | | | | | | | | | | | | | | This code sets up and calls the SbeRetryHandler class to attempt an SBE restart. Additionally, we need more than one way to restart the SBE: p9_start_cbs and hreset. This commit sets up the structure to use one of the two methods while waiting on hreset to be available. Change-Id: I17dfb4047268efa84e388391698b668cec2e13e4 RTC:180243 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/50953 Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com> Tested-by: Jenkins OP Build CI <op-jenkins+hostboot@us.ibm.com> Tested-by: FSP CI Jenkins <fsp-CI-jenkins+hostboot@us.ibm.com> Tested-by: Jenkins OP HW <op-hw-jenkins+hostboot@us.ibm.com> Reviewed-by: William G. Hoffa <wghoffa@us.ibm.com>
* Add call to get the SBE RC and commit it to an error logElizabeth Liner2017-12-221-2/+39
| | | | | | | | | | Change-Id: I9cb9a03a8c8530cf1476a0ddd4923fff43ca88ae RTC:180241 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/50952 Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com> Tested-by: Jenkins OP Build CI <op-jenkins+hostboot@us.ibm.com> Tested-by: FSP CI Jenkins <fsp-CI-jenkins+hostboot@us.ibm.com> Reviewed-by: William G. Hoffa <wghoffa@us.ibm.com>
* Add in a check in the PSU error logging for SBE failureElizabeth Liner2017-12-203-286/+164
| | | | | | | | | | | | | If there is an error in the PSU, and there is no FFDC, there is probably something wrong with the SBE. Since there is new support to attempt an SBE reboot if there's an error, we want to add that functionality to the PSU flow as well. Change-Id: I8203193b49caaf640962e181a814df83c0760ff4 RTC:178801 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/46641 Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com> Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com>
* Adding SbeRetryHandler to the runtime moduleElizabeth Liner2017-12-132-1/+30
| | | | | | | | | | | Change-Id: I08ef8fee920178bb4b806df8633626318c11ba0f RTC:180961 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/50380 Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com> Tested-by: FSP CI Jenkins <fsp-CI-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> Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com>
* Unit tests for SbeRetryHandlerElizabeth Liner2017-12-132-0/+245
| | | | | | | | | | | Change-Id: I86c25275c1fd218c10da8c604a971a342155b232 RTC:180961 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/50179 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: Daniel M. Crowell <dcrowell@us.ibm.com>
* SBE error logging and handler cleanupElizabeth Liner2017-12-134-723/+215
| | | | | | | | | | | | | | | | | | | | | | | This commit takes care of a few things 1) Removing the sbe threshold handler - we decided that retrying after the initial loop was overkill 2) Making use of the class structure - we added a lot of class elements to decrease things passed between functions and to facilitate debugging 3) Creating a main entry point and simplifying functions We decided that we wanted one function to handle all actions. This also made some function irrelevant and as such they were removed. Additionally, this also fixes an infinite circular logic bug. Change-Id: I9556e3181226755150c3debd1471f1be23e13be4 RTC:180961 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/49886 Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com> Tested-by: FSP CI Jenkins <fsp-CI-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> Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com>
* Adding more debugging traces to the SBE error handlerElizabeth Liner2017-12-112-12/+64
| | | | | | | | | | | | | Change-Id: I9c71969486d8160caa6e675ea91ba9aed5e088a9 RTC:180961 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/49109 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> Reviewed-by: William G. Hoffa <wghoffa@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: Daniel M. Crowell <dcrowell@us.ibm.com>
* Fixing the SBE switch functionalityElizabeth Liner2017-12-081-79/+119
| | | | | | | | | | | Change-Id: I121c121b8c58f3c44e748d91a88906ad1ca35d43 RTC:180961 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/49067 Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com> Reviewed-by: Martin Gloff <mgloff@us.ibm.com> Tested-by: FSP CI Jenkins <fsp-CI-jenkins+hostboot@us.ibm.com> Tested-by: Jenkins OP Build CI <op-jenkins+hostboot@us.ibm.com> Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com>
* Create base class structure for SbeRetryHandlerElizabeth Liner2017-12-084-59/+103
| | | | | | | | | | | | | | This commit restructures the sbe_extract_rc_handler code into its own class. Change-Id: Ib6ecb1a67353b060a6578b13da951b276bc93ca7 RTC:180961 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/48511 Reviewed-by: Martin Gloff <mgloff@us.ibm.com> Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com> Tested-by: FSP CI Jenkins <fsp-CI-jenkins+hostboot@us.ibm.com> Tested-by: Jenkins OP Build CI <op-jenkins+hostboot@us.ibm.com> Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com>
* Use readSeeprom PSU chipop to get SBE seeprom image versionChristian Geddes2017-11-172-0/+109
| | | | | | | | | | | | | | | | | | | | During an SBE update we were getting I2C collisions when trying to access pnor on the "running" or "active" side of the seeprom. This commit adds support for a PSU chipOp called "readSeeprom" which allows the host to make a request to the SBE to copy a specified chunk of pnor out to a buffer in memory which the host can access. This commit also uses this chipOp in place of the I2C read during the SBE update of the active seeprom side. Change-Id: I4b639ebe6090dcc0bdbb42f13fcb12c23260a8b4 RTC: 180959 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/48408 Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com> Reviewed-by: Matt Derksen <mderkse1@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: Daniel M. Crowell <dcrowell@us.ibm.com>
* Moving SBE threshold handler to its own fileElizabeth Liner2017-11-064-220/+379
| | | | | | | | | | | | | | | | The SBE extract code is being moved to a class structure, and since the FSM uses function pointers, we cannot easily implement a finite state machine. Change-Id: I380e53f0a78662c4f5dfd9e8db3cb6d4761a0be3 RTC:180961 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/48996 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: Martin Gloff <mgloff@us.ibm.com> Reviewed-by: William G. Hoffa <wghoffa@us.ibm.com>
* Centaur ring support - ring_apply and ring dataSumit Kumar2017-11-011-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - Introduces Centaur ring ID header files and ring_apply support to generate a separate Centaur ring image file. - Introduces common ring ID header file consumed by both P9 and Centaur and all user codes, e.g. putRing, ipl_build, xip_tool, etc. - Introduces a namespace approach for complete separation of P9 and Centaur ring data and to facilitate execution time selection of either P9 and Centaur ring data. - Added Centaur image .rings generation function to p9_ring_apply. - This commit does NOT support Centaur in the TOR API nor in xip_tool. See commit 38018 for that support. - Modified hw_image.mk file to support Centaur XIP image generation. - Updated ring_apply to also support .overrides ring gen for Centaur. Change-Id: I12a27b194dc14d906fea7bc273eb9f766f0fc5bf Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/35639 Tested-by: HWSV CI <hwsv-ci+hostboot@us.ibm.com> Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com> Tested-by: FSP CI Jenkins <fsp-CI-jenkins+hostboot@us.ibm.com> Reviewed-by: Sumit Kumar <sumit_kumar@in.ibm.com> Tested-by: PPE CI <ppe-ci+hostboot@us.ibm.com> Reviewed-by: Richard J. Knight <rjknight@us.ibm.com> Reviewed-by: Thi N. Tran <thi@us.ibm.com> Tested-by: Hostboot CI <hostboot-ci+hostboot@us.ibm.com> Reviewed-by: Jennifer A. Stofer <stofer@us.ibm.com> Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/36011 Reviewed-by: Hostboot Team <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> Reviewed-by: Christian R. Geddes <crgeddes@us.ibm.com>
* Additional checks to p9_extract_sbe_rcSoma BhanuTej2017-10-241-5/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | - To detect NDD1 or other chip for seeprom & otp addr upd - pibmem program exception - otprom program exception - Use sbe_cs bit to identify the state of pk loader - Adding CBS_STATUS_REGISTERS,ROOT_CTRL_REGISTERS in xml - Using ifndef __HOSTBOOT_MODULE while read MBOX registers - Update all Non-Secure mode RC names Change-Id: Ic764bbda94d9beb023aa1861cb143bf05b8ff06a RTC: 174954 CQ: SW404908 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/41738 Tested-by: FSP CI Jenkins <fsp-CI-jenkins+hostboot@us.ibm.com> Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com> Tested-by: HWSV CI <hwsv-ci+hostboot@us.ibm.com> Tested-by: PPE CI <ppe-ci+hostboot@us.ibm.com> Tested-by: Hostboot CI <hostboot-ci+hostboot@us.ibm.com> Reviewed-by: Soma Bhanutej <soma.bhanu@in.ibm.com> Reviewed-by: Joachim Fenkes <fenkes@de.ibm.com> Reviewed-by: Jennifer A. Stofer <stofer@us.ibm.com> Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/41770 Tested-by: Jenkins OP Build CI <op-jenkins+hostboot@us.ibm.com> Tested-by: Jenkins OP HW <op-hw-jenkins+hostboot@us.ibm.com> Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com>
* Secure Boot: Log SBE FIFO scom blacklist violationsNick Bofferding2017-10-191-0/+43
| | | | | | | | | | | | | | - Log SBE FIFO scom blacklist violations, but do not terminate system Change-Id: Ie857bb829471b67b5c08cf8a4a06da9ead050afb Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/48358 Reviewed-by: Stephen M. Cprek <smcprek@us.ibm.com> Reviewed-by: Michael Baiocchi <mbaiocch@us.ibm.com> Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com> Tested-by: FSP CI Jenkins <fsp-CI-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> Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com>
* Implement FAPI_PLAT_CALL_SUBROUTINE macroChristian Geddes2017-10-172-13/+9
| | | | | | | | | | | | | | | | | | | HWP writers need a way to request certain HWPs to run on the SBE for non-master processor targets while we are in secureBoot mode. This macro will check these conditions and if we are on a non-master in secureMode then we will issue a fifo chipop to the slave sbe in order to request the SBE to perform the HWP. This commit also adds some simple test cases to verify the failure paths. Also fapi2 test cases are re-enabled in this commit. Change-Id: Ic42fe2df5692fb5994985d92b2fd767ea7c1234a RTC: 179062 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/46580 Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com> Tested-by: Jenkins OP Build CI <op-jenkins+hostboot@us.ibm.com> Tested-by: FSP CI Jenkins <fsp-CI-jenkins+hostboot@us.ibm.com> Tested-by: Jenkins OP HW <op-hw-jenkins+hostboot@us.ibm.com> Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com>
* Add Hostboot infrastructure for secureHwp chipop requestChristian Geddes2017-10-153-0/+218
| | | | | | | | | | | | | | | | Create structs and methods required for issuing a secureHwp chipop request to the SBE. Change-Id: Id493fc59346ee2c7155bd09a88ac0cba22a29c42 RTC: 179062 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/46365 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> Reviewed-by: Brian E. Bakke <bbakke@us.ibm.com> Tested-by: FSP CI Jenkins <fsp-CI-jenkins+hostboot@us.ibm.com> Reviewed-by: Martin Gloff <mgloff@us.ibm.com> Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com>
OpenPOWER on IntegriCloud