talos-hostboot/src/include/usr/sbeio, branch master

Add error log for sbe poweron fails and clean up errlog commits

2018-05-07T20:13:03+00:00

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 Tested-by: Jenkins OP Build CI Tested-by: Jenkins OP HW Tested-by: FSP CI Jenkins Reviewed-by: Martin Gloff Reviewed-by: Brian E. Bakke Reviewed-by: Roland Veloz Reviewed-by: Daniel M. Crowell

Add support to find relocated payload base address

2018-04-19T21:57:04+00:00

OPAL relocates itself after boot. During MPIPL, hostboot needs to access relocated SPIRAH. Hence lets add support to get relocated payload base address. OPAL will use SBE stash chip-op to send relocated address to SBE. During early IPL SBE sends stashed data to hostboot. And hostboot will use that information to find relocated payload (OPAL) base. SBE stash chip op: key = 0x03 val = Change-Id: I1089bd38f32b01b877d1580ba76313fc250e5c08 Signed-off-by: Vasant Hegde Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/55190 Tested-by: Jenkins Server Tested-by: Jenkins OP Build CI Tested-by: Jenkins OP HW Reviewed-by: Christian R. Geddes Tested-by: FSP CI Jenkins Reviewed-by: Daniel M. Crowell

Improve linking of PLIDs for sbe_retry_handler

2018-04-13T17:34:41+00:00

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 Tested-by: Jenkins Server Tested-by: Jenkins OP Build CI Tested-by: Jenkins OP HW Tested-by: FSP CI Jenkins Reviewed-by: Daniel M. Crowell

Revert "Clear perv scrach register prior to triggering HRESET"

2018-04-10T20:02:42+00:00

This reverts commit 4f32915aa1240d07bb2671010f95695ba5f306c3. Change-Id: Ie51fd274d018df63aef6f725bf57c7b1f7f59265 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/57026 CI-Ready: Christian R. Geddes Reviewed-by: Christian R. Geddes Tested-by: Christian R. Geddes

Clear perv scrach register prior to triggering HRESET

2018-04-10T19:54:44+00:00

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 Tested-by: Jenkins Server Tested-by: Jenkins OP Build CI CI-Ready: Christian R. Geddes Tested-by: Jenkins OP HW Reviewed-by: Roland Veloz Reviewed-by: Daniel M. Crowell

Enable OpenPower SBE Vital Attention handler

2018-04-10T17:46:19+00:00

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 Reviewed-by: Martin Gloff Tested-by: Jenkins Server Tested-by: Jenkins OP Build CI Tested-by: Jenkins OP HW Tested-by: FSP CI Jenkins Reviewed-by: Roland Veloz Reviewed-by: Daniel M. Crowell

Hook up FSP runtime support for sbe_retry_handler (hreset path)

2018-04-09T18:31:53+00:00

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 Tested-by: Jenkins Server Tested-by: Jenkins OP Build CI Tested-by: Jenkins OP HW Reviewed-by: Roland Veloz Tested-by: FSP CI Jenkins Reviewed-by: Daniel M. Crowell

sbe_retry_handler refactor

2018-04-06T14:15:43+00:00

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 Tested-by: Jenkins OP Build CI Tested-by: Jenkins OP HW Reviewed-by: Daniel M. Crowell Tested-by: Daniel M. Crowell

Inform OPAL of the state of the SBE after an attempt to restart

2018-03-22T14:00:57+00:00

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 Tested-by: Jenkins OP Build CI Tested-by: Jenkins OP HW Tested-by: FSP CI Jenkins Reviewed-by: Martin Gloff Reviewed-by: Christian R. Geddes Reviewed-by: Daniel M. Crowell

Adding visible error once we know that the SBE is erroring

2018-02-27T18:05:58+00:00

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 Tested-by: Jenkins OP Build CI Tested-by: Jenkins OP HW Tested-by: FSP CI Jenkins Reviewed-by: Roland Veloz CI-Ready: Christian R. Geddes Reviewed-by: Christian R. Geddes Reviewed-by: Martin Gloff Reviewed-by: William G. Hoffa