From d7355b73ce6b9b6b2a8634a4f349d3ca2c25104c Mon Sep 17 00:00:00 2001 From: Marty Gloff Date: Mon, 23 Apr 2018 12:01:45 -0500 Subject: Improve resource recovery path to handle memory plugging rules 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 --- .../targeting/common/xmltohb/attribute_types.xml | 23 ++++++++++++++++++++++ 1 file changed, 23 insertions(+) (limited to 'src/usr/targeting/common/xmltohb/attribute_types.xml') diff --git a/src/usr/targeting/common/xmltohb/attribute_types.xml b/src/usr/targeting/common/xmltohb/attribute_types.xml index ab456ceaf..0c37f955d 100755 --- a/src/usr/targeting/common/xmltohb/attribute_types.xml +++ b/src/usr/targeting/common/xmltohb/attribute_types.xml @@ -495,6 +495,25 @@ + + Block speculative deconfig in reconfig loop. + Flags when speculative deconfigurations should not be done for + predictive gard records on a reconfig loop IPL due to out of + hardware condition on prior IPL. + 0 = Allow speculative deconfiguration + 1 = Block speculative deconfiguration + + BLOCK_SPEC_DECONFIG + non-volatile + + + + 0x0 + + + + + Numeric POD type test structure @@ -5092,6 +5111,10 @@ HOSTSVC_HBEL 0x00000008 + + RESRC_RECOV + 0x00000010 + HWAS_CHANGED_BIT -- cgit v1.2.1