OpenPOWER support for native and compatibility mode for DD2.3

Witherspoon (OpenPOWER) will run in native mode, which means
all the processors have to be at the same level
(all DD2.2 or all DD2.3). Other systems (ZZ) we support
running in a mixed configuration where DD2.3 processors will
be run in 2.2 compatibility mode.  We also need to support
arbitrary OP systems that might want to run in compatibility
mode even without mixed parts.

See src/usr/hwas/common/README.md for the rules and resulting
mode.

Change-Id: I80fb98e2687b945ba506f2d75b1533884443e10b
RTC:201485
Reviewed-on: http://rchgit01.rchland.ibm.com/gerrit1/72214
Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com>
Reviewed-by: Christian R. Geddes <crgeddes@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>

1 files changed, 68 insertions, 1 deletions

diff --git a/src/usr/targeting/common/xmltohb/attribute_types.xml b/src/usr/targeting/common/xmltohb/attribute_types.xml
index 21eca1fd7..065c65307 100644
--- a/src/usr/targeting/common/xmltohb/attribute_types.xml
+++ b/src/usr/targeting/common/xmltohb/attribute_types.xml
@@ -5845,7 +5845,7 @@
     <description>
        Tracks if a specific core has previously experienced a timeout during
        initial activation.
-          0 = No previous errors reported; 
+          0 = No previous errors reported;
           1 = Core failed on the last attempt to be started
     </description>
     <id>PREVIOUS_WAKEUP_FAIL</id>
@@ -5905,6 +5905,41 @@
   </attribute>
 
   <attribute>
+    <description>Required Processor Compatibility Setting</description>
+    <id>PROC_COMPATIBILITY_REQ</id>
+    <persistency>non-volatile</persistency>
+    <readable/>
+    <simpleType>
+      <enumeration>
+        <id>PROC_COMPATIBILITY_REQ</id>
+      </enumeration>
+    </simpleType>
+  </attribute>
+
+  <enumerationType>
+    <default>ALLOW_COMPATIBILITY</default>
+    <description>
+        Enumeration specifying the compatibility setting for Processor ECs
+        ALLOW_COMPATIBILITY = set RISK_LEVEL to best allowed
+        FORCED_COMPATIBILITY = set RISK_LEVEL to a compatible level
+        FORCED_NATIVE = set RISK_LEVEL to ECs native setting
+    </description>
+    <enumerator>
+      <name>ALLOW_COMPATIBILITY</name>
+      <value>0</value>
+    </enumerator>
+    <enumerator>
+      <name>FORCED_COMPATIBILITY</name>
+      <value>1</value>
+    </enumerator>
+    <enumerator>
+      <name>FORCED_NATIVE</name>
+      <value>2</value>
+    </enumerator>
+    <id>PROC_COMPATIBILITY_REQ</id>
+  </enumerationType>
+
+  <attribute>
     <id>PROC_DCM_INSTALLED</id>
     <description>
       PROC_CHIP Attribute
@@ -6644,6 +6679,38 @@
   </attribute>
 
   <attribute>
+    <description>Where did the RISK_LEVEL setting originate?
+    This is used to make sure the MRW isn't setting an invalid level
+    for FORCED_COMPATIBILITY.
+    </description>
+    <id>RISK_LEVEL_ORIGIN</id>
+    <persistency>volatile-zeroed</persistency>
+    <readable/>
+    <simpleType>
+      <enumeration>
+        <id>RISK_LEVEL_ORIGIN</id>
+      </enumeration>
+    </simpleType>
+    <writeable/>
+  </attribute>
+
+  <enumerationType>
+    <default>USER</default>
+    <description>
+        Enumeration specifying what was used to setup the RISK_LEVEL
+    </description>
+    <enumerator>
+      <name>USER</name>
+      <value>0</value>
+    </enumerator>
+    <enumerator>
+      <name>MRW</name>
+      <value>1</value>
+    </enumerator>
+    <id>RISK_LEVEL_ORIGIN</id>
+  </enumerationType>
+
+  <attribute>
     <description>Size of RNG IO Region</description>
     <id>RNG_BAR_SIZE</id>
     <persistency>non-volatile</persistency>