Fixing bulk_pwr_throttles calculations

Change-Id: Icda72ae4f7d9944aea3bd9719555e470ad79fda1
Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/32138
Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com>
Reviewed-by: Michael D. Pardeik <pardeik@us.ibm.com>
Reviewed-by: Brian R. Silver <bsilver@us.ibm.com>
Tested-by: Hostboot CI <hostboot-ci+hostboot@us.ibm.com>
Reviewed-by: Christian R. Geddes <crgeddes@us.ibm.com>
Dev-Ready: Brent Wieman <bwieman@us.ibm.com>
Reviewed-by: Brent Wieman <bwieman@us.ibm.com>
Reviewed-by: Jennifer A. Stofer <stofer@us.ibm.com>
Reviewed-on: http://rchgit01.rchland.ibm.com/gerrit1/69792
Reviewed-by: Sachin Gupta <sgupta2m@in.ibm.com>
Tested-by: Sachin Gupta <sgupta2m@in.ibm.com>

src/import/chips/p9/procedures/xml/attribute_info/memory_mcs_attributes.xml

@@ -1197,6 +1197,19 @@
         <mssAccessorName>mem_throttled_n_commands_per_port</mssAccessorName>
     </attribute>
 
+    <attribute>
+        <id>ATTR_MSS_MEM_PORT_POS_OF_FAIL_THROTTLE</id>
+        <targetType>TARGET_TYPE_SYSTEM</targetType>
+        <description>
+          This is the fapi position of the port that failed to calculate
+          memory throttles given the passed in watt target and or utilization
+        </description>
+        <initToZero></initToZero>
+        <valueType>uint64</valueType>
+        <writeable/>
+        <mssAccessorName>mem_port_fail_throttle</mssAccessorName>
+    </attribute>
+
     <attribute>
         <id>ATTR_MSS_MEM_M_DRAM_CLOCKS</id>
         <targetType>TARGET_TYPE_MCS</targetType>
@@ -1332,7 +1345,7 @@
         <id>ATTR_MSS_DATABUS_UTIL</id>
         <targetType>TARGET_TYPE_MCS</targetType>
         <description>
-            Databus utilization limit used to calculate memory throttles and power limit
+            Databus utilization per port limit used to calculate memory throttles and power limit
             creator: OCC
             consumer: mss_utils_to_throttle
         </description>