Fix issue 294: incorrect ParentCategory for Serializing_Operation and AMX_Busy

Metrics Serializing_Operation and AMX_Busy have incorrect ParentCategory value: Ports_Utilized_0
This commit replace the parent to Core_Bound as specified in the TMA Excel file.

Signed-off-by: Laksono Adhianto <[email protected]>

Author: laksono

SPR/metrics/sapphirerapids_metrics.json

@@ -7444,7 +7444,7 @@
     {
       "MetricName": "Serializing_Operation",
       "LegacyName": "metric_TMA_....Serializing_Operation(%)",
-      "ParentCategory": "Ports_Utilized_0",
+      "ParentCategory": "Core_Bound",
       "Level": 3,
       "BriefDescription": "This metric represents fraction of cycles the CPU issue-pipeline was stalled due to serializing operations. Instructions like CPUID; WRMSR or LFENCE serialize the out-of-order execution which may limit performance.",
       "UnitOfMeasure": "percent",
@@ -7689,7 +7689,7 @@
     {
       "MetricName": "AMX_Busy",
       "LegacyName": "metric_TMA_....AMX_Busy(%)",
-      "ParentCategory": "Ports_Utilized_0",
+      "ParentCategory": "Core_Bound",
       "Level": 3,
       "BriefDescription": "This metric estimates fraction of cycles where the Advanced Matrix eXtensions (AMX) execution engine was busy with tile (arithmetic) operations",
       "UnitOfMeasure": "percent",
@@ -14660,4 +14660,4 @@
       "LocateWith": ""
     }
   ]
-}
+}