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 <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>

1 files changed, 23 insertions, 0 deletions

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
@@ -496,6 +496,25 @@
   </attribute>
 
   <attribute>
+    <description>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
+        </description>
+    <id>BLOCK_SPEC_DECONFIG</id>
+    <persistency>non-volatile</persistency>
+    <readable></readable>
+    <simpleType>
+      <uint8_t>
+        <default>0x0</default>
+      </uint8_t>
+    </simpleType>
+    <writeable></writeable>
+  </attribute>
+
+  <attribute>
     <complexType>
       <description>Numeric POD type test structure</description>
       <field>
@@ -5092,6 +5111,10 @@
       <name>HOSTSVC_HBEL</name>
       <value>0x00000008</value>
     </enumerator>
+    <enumerator>
+      <name>RESRC_RECOV</name>
+      <value>0x00000010</value>
+    </enumerator>
     <id>HWAS_CHANGED_BIT</id>
   </enumerationType>