RAS/AMD/ATL: Add MI300 support
AMD MI300 systems include on-die HBM3 memory and a unique topology. And they fall under Data Fabric version 4.5 in overall design. Generally, topology information (IDs, etc.) is gathered from Data Fabric registers. However, the unique topology for MI300 means that some topology information is fixed in hardware and follows arbitrary mappings. Furthermore, not all hardware instances are software-visible, so register accesses must be adjusted. Recognize and add helper functions for the new MI300 interleave modes. Add lookup tables for fixed values where appropriate. Adjust how Die and Node IDs are found and used. Also, fix some register bitmasks that were mislabeled. Signed-off-by: Muralidhara M K <muralidhara.mk@amd.com> Co-developed-by: Yazen Ghannam <yazen.ghannam@amd.com> Signed-off-by: Yazen Ghannam <yazen.ghannam@amd.com> Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de> Link: https://lore.kernel.org/r/20240128155950.1434067-1-yazen.ghannam@amd.com
This commit is contained in:
committed by
Borislav Petkov (AMD)
parent
1289c43164
commit
453f0ae797
@@ -124,6 +124,9 @@ static int df4_determine_df_rev(u32 reg)
|
||||
if (reg == DF_FUNC0_ID_ZEN4_SERVER)
|
||||
df_cfg.flags.socket_id_shift_quirk = 1;
|
||||
|
||||
if (reg == DF_FUNC0_ID_MI300)
|
||||
df_cfg.flags.heterogeneous = 1;
|
||||
|
||||
return df4_get_fabric_id_mask_registers();
|
||||
}
|
||||
|
||||
|
||||
Reference in New Issue
Block a user