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

Verify frequency attributes across nodes to match with that of master node

2018-05-16T16:51:54+00:00

-Existing code ensures consistency of frequency data across all modules in istep6.12. -In a multi-drawer config this data needs to be consistent across all drawers. -Master drawer sends the frequency data to all the other via IPC mechanism. -This data is compared and error is returned if there is a mismatch. Change-Id: Ia1daf1f0eeb90fbafb68417b979488b040efe535 RTC:158036 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/57542 Reviewed-by: Prachi Gupta 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

Improve resource recovery path to handle memory plugging rules

2018-05-15T22:08:42+00:00

Resource recovery is a RAS feature wherein we do not apply certain gard records if those records would result in a boot fail due to a lack of hardware. Change the logic from applying speculative deconfiguration one by one to applying all predictive gard records and then removing those records if minimal hardware is not available. Also add BLOCK_SPEC_DECONFIG attribute to flag when speculative deconfiguration is not allowed. This flag is set if minimum hardware is not available and is cleared after a hardware change. Change-Id: Ia065de3a44ab29fbf33ad4ce98bc42ea5144463f RTC: 191414 CQ: SW424137 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/58041 Tested-by: Jenkins Server Tested-by: Jenkins OP Build CI Tested-by: Jenkins OP HW Tested-by: FSP CI Jenkins Reviewed-by: Christian R. Geddes Reviewed-by: Daniel M. Crowell

wrap_test: OBUS deconfiguration

2018-04-27T18:54:07+00:00

Due to fabric limitations, we can only have 2 OBUSes enabled at a time. This commit deconfigures the OBUSes that do not belong the set of links to enable in this boot based on attributes. Change-Id: I15f5e9f3ea186367b9c4d55f4dc2e9b32b251f6d Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/57836 Tested-by: Jenkins Server Tested-by: Jenkins OP Build CI Tested-by: FSP CI Jenkins Tested-by: Jenkins OP HW Reviewed-by: Elizabeth K. Liner Reviewed-by: Roland Veloz Reviewed-by: Martin Gloff Reviewed-by: William G. Hoffa

Add deconfigTargetAtRuntime interface

2018-04-12T20:31:07+00:00

-PRD will call this function in response to a core unit checkstop detected by PHYP. The new function will mark the core as non-functional and call a hardware procdure to update the multicast groups for cores and chiplets. The procedure will also update the OCC core configuration status and the quad core status registers which reflect the number of enable cores/quad in the system at runtime. Change-Id: Ia7fc3f47dc1fee1f84d877d3d56b609d1aee1b17 RTC:188918 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/55154 Tested-by: Jenkins Server Reviewed-by: Richard Ward Reviewed-by: Christian R. Geddes Tested-by: FSP CI Jenkins Tested-by: Jenkins OP Build CI Tested-by: Jenkins OP HW Reviewed-by: William G. Hoffa

Revert "Verify frequency attributes across nodes"

2018-04-09T13:41:07+00:00

This reverts commit 571e1d84dfe50aaa674aa7e33abb75868b432d78. Change-Id: I8720246ef94be07ce0a37151b7209c8080320d59 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/56933 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

Verify frequency attributes across nodes

2018-04-05T18:34:23+00:00

-Existing code ensures consistency of frequency data across all modules in istep6.12. -In a multi-drawer config this data needs to be consistent across all drawers. -Master drawer sends the frequency data to all the other via IPC mechanism. -This data is compared and error is returned if there is a mismatch. Change-Id: I922d32456c9d3c4e53dae528f088dbb013c3ded9 RTC:158036 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/54825 CI-Ready: SWATHI M. BHATTIPROLU Reviewed-by: Daniel M. Crowell Tested-by: Jenkins Server Reviewed-by: Richard Ward Tested-by: Jenkins OP Build CI Tested-by: Jenkins OP HW Tested-by: FSP CI Jenkins Reviewed-by: William G. Hoffa

Clear FCO deconfigures before applying gard records

2018-03-01T14:48:25+00:00

When an EX is deconfigured, its parent EQ is deconfigured by association if all resources under it happen to be deconfigured, even if some of those resources are FCO deconfigures. Later, FCO deconfigures are removed to determine a new FCO allocation. If an FCO resource is allocated under that deconfigured EQ, the system may not boot, as those resources will appear to be orphaned. This change reorders FCO/gard processing to clear the FCO deconfigures, apply gard records, then allocate FCO resources, so that the EQ in the noted scenario remains configured, allowing child FCO resources to be used. CQ: SW417765 Change-Id: I22817b0bae0df0dfabd7e02ec8afa91033e092ca Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/54738 CI-Ready: Nicholas E. Bofferding Tested-by: Jenkins Server Tested-by: Jenkins OP Build CI Tested-by: Jenkins OP HW Reviewed-by: ILYA SMIRNOV CI-Ready: Marshall J. Wilks Reviewed-by: Michael Baiocchi Tested-by: FSP CI Jenkins Reviewed-by: DHRUVARAJ SUBHASH CHANDRAN Reviewed-by: Daniel M. Crowell

Support for any target deconfig at runtime; Utility to create a generic message

2018-01-17T21:08:40+00:00

I added code to inform FSP whenever a target has been deconfiged. I also added a handy utility to facilitate in the construction of a Generic FSP message. Change-Id: Iad755d4de1bf200ab00ad3f99451512ba8cdabb4 RTC: 183950 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/51201 Reviewed-by: Martin Gloff Reviewed-by: Christian R. Geddes Tested-by: Jenkins Server Reviewed-by: Daniel M. Crowell

Stop deconfiguring magic MCA and its MCBIST by association

2017-12-15T16:11:30+00:00

Deconfiguring the magic MCA and its parent MCBIST was causing Maint UE to be reported on other slots. The deconfiguration logic for magic MCAs will now be handled by the RC_MSS_ZCNTL hardware procedure. Change-Id: Ica32c3b5850ae6e7b9f6c2a53bfcb88d4b462046 CQ:SW402588 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/50842 Tested-by: Jenkins Server Tested-by: FSP CI Jenkins Tested-by: Jenkins OP Build CI Tested-by: Jenkins OP HW Reviewed-by: Daniel M. Crowell Reviewed-by: Prachi Gupta Reviewed-by: William G. Hoffa

TI w/ unrecoverable error if system boots w/ mismatching processors

2017-12-08T16:56:02+00:00

We do not support processor modules w/ different EC levels to be on the same system. The rule is that all processors must match the master processor. If this is not true then hostboot will TI. Techically we could probably still boot and just gard out the non-matching proc's but the use case for this will be lab/manufac. For those cases we want the technician to know right away that they put a module w/ the wrong DD level in a system. RTC: 183243 Change-Id: I09b30550edd30c8523fd2a709c7b7a83f597eab8 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/50167 Reviewed-by: Matt Derksen Reviewed-by: Martin Gloff Tested-by: Jenkins Server Tested-by: FSP CI Jenkins Tested-by: Jenkins OP Build CI Reviewed-by: Daniel M. Crowell