x86/edac/amd64: Add heterogeneous node support
Subsystems (4)
v6 cover x86/edac/amd64: Add heterogeneous node support
On newer heterogeneous systems with AMD CPUs the data fabrics of GPUs can be connected directly via custom links.
This series of patchset does the following
1. amd_nb.c:
a. Add support for northbridges on Aldebaran GPU nodes b. export AMD node map details to be used by edac and mce modules
2. mce_amd module:
a. Identify the node ID where the error occurred and map the node
id to linux enumerated node id.
3. amd64_edac module
a. Add new family op routines
b. Enumerate UMCs and HBMs on the GPU nodes c. Move fam_type structure into amd64_pvt struct
This patchset is rebased on top of
"
commit 07416cadfdfa38283b840e700427ae3782c76f6b
Author: Yazen Ghannam <[email protected]> Date: Tue Oct 5 15:44:19 2021 +0000
EDAC/amd64: Handle three rank interleaving mode
"
Muralidhara M K (3):
x86/amd_nb: Add support for northbridges on Aldebaran EDAC/amd64: Extend family ops functions EDAC/amd64: Move struct fam_type into amd64_pvt structure
Naveen Krishna Chatradhi (2):
EDAC/mce_amd: Extract node id from MCA_IPID EDAC/amd64: Enumerate memory on Aldebaran GPU nodes
arch/x86/include/asm/amd_nb.h | 9 + arch/x86/kernel/amd_nb.c | 146 ++++++-- drivers/edac/amd64_edac.c | 654 ++++++++++++++++++++++++---------- drivers/edac/amd64_edac.h | 39 +- drivers/edac/mce_amd.c | 24 +- include/linux/pci_ids.h | 1 + 6 files changed, 663 insertions(+), 210 deletions(-)
Signature · 1 line
2.25.1
PATCH v6 1/5 x86/amd_nb: Add support for northbridges on Aldebaran
From: Muralidhara M K <[email protected]>
On newer systems the CPUs manage MCA errors reported from the GPUs. Enumerate the GPU nodes with the AMD NB framework to support EDAC.
GPU nodes are enumerated in sequential order based on the PCI hierarchy, and the first GPU node is assumed to have an "AMD Node ID" value after CPU Nodes are fully populated.
Aldebaran is an AMD GPU, GPU drivers are part of the DRM framework
https://lists.freedesktop.org/archives/amd-gfx/2021-February/059694.html
Each Aldebaran GPU has 2 Data Fabrics, which are enumerated as 2 nodes. With this implementation detail, the Data Fabric on the GPU nodes can be accessed the same way as the Data Fabric on CPU nodes.
Special handling was necessary in northbridge enumeration as the roots_per_misc value is different for GPU and CPU nodes.
---
Changes since v5:
Modified amd_get_node_map() and checking return value
Changes since v4:
1. renamed struct name from nmap to nodemap
2. split amd_get_node_map and addressed minor comments
Changes since v3:
1. Use word "gpu" instead of "noncpu" in the patch
2. Do not create pci_dev_ids arrays for gpu nodes
3. Identify the gpu node start index from DF18F1 registers on the GPU nodes. a. Export cpu node count and gpu start node id
Changes since v2:
1. Added Reviewed-by Yazen Ghannam
Changes since v1:
1. Modified the commit message and comments in the code
2. Squashed patch 1/7: "x86/amd_nb: Add Aldebaran device to PCI IDs"
arch/x86/include/asm/amd_nb.h | 9 +++ arch/x86/kernel/amd_nb.c | 146 ++++++++++++++++++++++++++++------ include/linux/pci_ids.h | 1 + 3 files changed, 133 insertions(+), 23 deletions(-)
arch/x86/include/asm/amd_nb.h +9 -0
@@ -68,10 +68,17 @@ struct amd_northbridge {struct threshold_bank *bank4; }; +/* heterogeneous system node type map variables */ +struct amd_node_map { +u16 gpu_node_start_id; +u16 cpu_node_count; +}; +struct amd_northbridge_info {u16 num;u64 flags;struct amd_northbridge *nb; +struct amd_node_map *nodemap; };#define AMD_NB_GART BIT(0)
@@ -83,6 +90,8 @@ struct amd_northbridge_info {u16 amd_nb_num (void );bool amd_nb_has_feature (unsigned int feature);struct amd_northbridge *node_to_amd_nb (int node); +u16 amd_gpu_node_start_id (void ); +u16 amd_cpu_node_count (void );static inline u16 amd_pci_dev_to_node_id (struct pci_dev *pdev) {
arch/x86/kernel/amd_nb.c +123 -23
223 lines not on this page · raw message
include/linux/pci_ids.h +1 -0
@@ -557,6 +557,7 @@#define PCI_DEVICE_ID_AMD_19H_DF_F3 0x1653#define PCI_DEVICE_ID_AMD_19H_M40H_DF_F3 0x167c#define PCI_DEVICE_ID_AMD_19H_M50H_DF_F3 0x166d +#define PCI_DEVICE_ID_AMD_ALDEBARAN_DF_F3 0x14d3#define PCI_DEVICE_ID_AMD_CNB17H_F3 0x1703#define PCI_DEVICE_ID_AMD_LANCE 0x2000#define PCI_DEVICE_ID_AMD_LANCE_HOME 0x2001
Signature · 1 line
2.25.1
Borislav Petkov
maintainerRe: [PATCH v6 1/5] x86/amd_nb: Add support for northbridges on Aldebaran
arch/x86/kernel/amd_nb.c struct amd_northbridge *node_to_amd_nb(int node) · line 157
Quoted 6 lines · Naveen Krishna Chatradhi
arch/x86/kernel/amd_nb.c +6
-0+/* GPU Data Fabric ID Device 24 Function 1 */ +#define PCI_DEVICE_ID_AMD_ALDEBARAN_DF_F1 0x14d1 + +/* DF18xF1 registers on Aldebaran GPU */ +#define REG_LOCAL_NODE_TYPE_MAP 0x144 +#define REG_RMT_NODE_TYPE_MAP 0x148
Move those defines up, along with the rest of them. While at it, you can align them all vertically.
arch/x86/kernel/amd_nb.c struct amd_northbridge *node_to_amd_nb(int node) · line 160
Quoted 3 lines
arch/x86/kernel/amd_nb.c +3
-0+ +/* +* Newer AMD CPUs and GPUs whose data fabrics can be connected via custom xGMI
"Newer" is a commit message type of adjective and doesn't belong in permanent comments because when years pass, they won't be "newer" anymore. IOW, you can simply drop it here.
Quoted 1 line
+ * links, comes with registers to gather local and remote node type map info.
"come"
Quoted 3 lines
+ *
+ * "Local Node Type" refers to nodes with the same type as that from which the
+ * register is read, and "Remote Node Type" refers to nodes with a different type.
This sure sounds weird.
With my simplistic thinking I'd assume "local" is the CPU and "remote" is the GPU...
Quoted 7 lines
+ * This function, reads the registers from GPU DF function 1.
+ * Hence, local nodes are GPU and remote nodes are CPUs.
+ */arch/x86/kernel/amd_nb.c +4
-0+static int amd_get_node_map (void ) +{ +struct amd_node_map *nodemap; +struct pci_dev *pdev;
arch/x86/kernel/amd_nb.c struct amd_northbridge *node_to_amd_nb(int node) · line 182
Quoted 10 lines
arch/x86/kernel/amd_nb.c +10
-0+u32 tmp; + + pdev =pci_get_device (PCI_VENDOR_ID_AMD , +PCI_DEVICE_ID_AMD_ALDEBARAN_DF_F1 ,NULL ); +if (!pdev) { +pr_debug ("DF Func1 PCI device not found on this node.\n" ); +return -ENODEV ; + } + + nodemap =kmalloc (sizeof (*nodemap),GFP_KERNEL );
You allocate a whopping 4 bytes? Just do
struct amd_node_map nodemap;
in the nb info descriptor.
I still need to see whether those node maps and functions you're adding and exporting even make sense but that will happen later.
arch/x86/kernel/amd_nb.c struct amd_northbridge *node_to_amd_nb(int node) · line 186
Quoted 4 lines
arch/x86/kernel/amd_nb.c +4
-0+if (!nodemap) +return -ENOMEM ; + +pci_read_config_dword (pdev,REG_LOCAL_NODE_TYPE_MAP , &tmp);
Check retval.
arch/x86/kernel/amd_nb.c struct amd_northbridge *node_to_amd_nb(int node) · line 189
Quoted 3 lines
arch/x86/kernel/amd_nb.c +3
-0+ nodemap->gpu_node_start_id = tmp &0xFFF ; + +pci_read_config_dword (pdev,REG_RMT_NODE_TYPE_MAP , &tmp);
Ditto.
Quoted 10 lines
arch/x86/kernel/amd_nb.c +6
-0+ nodemap->cpu_node_count = tmp >>16 &0xFFF ; + + amd_northbridges.nodemap = nodemap; +return 0 ; +} +static struct pci_dev *next_northbridge (struct pci_dev *dev,const struct pci_device_id *ids) {
arch/x86/kernel/amd_nb.c int amd_df_indirect_read(u16 node, u8 func, u16 reg, u8 instance_id, u32 *lo) · line 300
Quoted 4 lines
arch/x86/kernel/amd_nb.c +1
-0@@ -230,6 +297,27 @@ int amd_df_indirect_read(u16 node, u8 func, u16 reg, u8 instance_id, u32 *lo) }EXPORT_SYMBOL_GPL (amd_df_indirect_read); +struct pci_dev *get_root_devs(struct pci_dev *root,
static
Quoted 39 lines
arch/x86/kernel/amd_nb.c +24
-4+const struct pci_device_id *root_ids, + u16 roots_per_misc) +{ + u16 j; + +/* +* If there are more PCI root devices than data fabric/ +* system management network interfaces, then the (N) +* PCI roots per DF/SMN interface are functionally the +* same (for DF/SMN access) and N-1 are redundant. N-1 +* PCI roots should be skipped per DF/SMN interface so +* the following DF/SMN interfaces get mapped to +* correct PCI roots. +*/ +for (j =0 ; j < roots_per_misc; j++) + root =next_northbridge (root, root_ids); + +return root; +} +int amd_cache_northbridges (void ) {const struct pci_device_id *misc_ids = amd_nb_misc_ids;@@ -237,10 +325,10 @@ int amd_cache_northbridges(void)const struct pci_device_id *root_ids = amd_root_ids;struct pci_dev *root, *misc, *link;struct amd_northbridge *nb; -u16 roots_per_misc =0 ; -u16 misc_count =0 ; -u16 root_count =0 ; -u16 i, j; +u16 roots_per_misc =0 , gpu_roots_per_misc =0 ; +u16 misc_count =0 , gpu_misc_count =0 ; +u16 root_count =0 , gpu_root_count =0 ; +u16 i;if (amd_northbridges.num)return 0 ;
arch/x86/kernel/amd_nb.c int amd_cache_northbridges(void) · line 343
Quoted 6 lines
arch/x86/kernel/amd_nb.c +1
-2@@ -252,15 +340,23 @@ int amd_cache_northbridges(void) } misc =NULL ; -while ((misc =next_northbridge (misc, misc_ids)) !=NULL ) - misc_count++; +while ((misc =next_northbridge (misc, misc_ids)) !=NULL ) {
Just remove that redundant "!= NULL" at the end, while at it.
Quoted 22 lines
arch/x86/kernel/amd_nb.c +11
-2+if (misc->device ==PCI_DEVICE_ID_AMD_ALDEBARAN_DF_F3 ) + gpu_misc_count++; +else + misc_count++; + }if (!misc_count)return -ENODEV ; root =NULL ; -while ((root =next_northbridge (root, root_ids)) !=NULL ) - root_count++; +while ((root =next_northbridge (root, root_ids)) !=NULL ) { +if (root->device ==PCI_DEVICE_ID_AMD_ALDEBARAN_ROOT ) + gpu_root_count++; +else + root_count++; + }if (root_count) { roots_per_misc = root_count / misc_count;
arch/x86/kernel/amd_nb.c int amd_cache_northbridges(void) · line 379
Quoted 10 lines
arch/x86/kernel/amd_nb.c +6
-1@@ -275,33 +371,37 @@ int amd_cache_northbridges(void) } } - nb =kcalloc (misc_count,sizeof (struct amd_northbridge ),GFP_KERNEL ); +/* +* The number of miscs, roots and roots_per_misc might vary on different +* nodes of a heterogeneous system. +* Calculate roots_per_misc accordingly in order to skip the redundant +* roots and map the DF/SMN interfaces to correct PCI roots. +*/
Reflow that comment so that it is a block.
arch/x86/kernel/amd_nb.c int amd_cache_northbridges(void) · line 382
Quoted 3 lines
arch/x86/kernel/amd_nb.c +3
-0+if (gpu_root_count && gpu_misc_count) { +int ret =amd_get_node_map (); +
^ Superfluous newline.
Quoted 6 lines
arch/x86/kernel/amd_nb.c +6
-0+if (ret) +return ret; + + gpu_roots_per_misc = gpu_root_count / gpu_misc_count; + } +
Signature · 4 lines
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquetteBorislav Petkov
maintainerRe: [PATCH v6 1/5] x86/amd_nb: Add support for northbridges on Aldebaran
In reply to Naveen Krishna ChatradhiOn Thu, Oct 28, 2021 at 06:31:02PM +0530, Naveen Krishna Chatradhi wrote:
Staring at this more...
arch/x86/kernel/amd_nb.c struct amd_northbridge *node_to_amd_nb(int node) · line 169
Quoted 11 lines
arch/x86/kernel/amd_nb.c +11
-0+/* +* Newer AMD CPUs and GPUs whose data fabrics can be connected via custom xGMI +* links, comes with registers to gather local and remote node type map info. +* +* "Local Node Type" refers to nodes with the same type as that from which the +* register is read, and "Remote Node Type" refers to nodes with a different type. +* +* This function, reads the registers from GPU DF function 1. +* Hence, local nodes are GPU and remote nodes are CPUs. +*/ +static int amd_get_node_map (void )
... so this is a generic function name...
arch/x86/kernel/amd_nb.c struct amd_northbridge *node_to_amd_nb(int node) · line 176
Quoted 7 lines
arch/x86/kernel/amd_nb.c +7
-0+{ +struct amd_node_map *nodemap; +struct pci_dev *pdev; +u32 tmp; + + pdev =pci_get_device (PCI_VENDOR_ID_AMD , +PCI_DEVICE_ID_AMD_ALDEBARAN_DF_F1 ,NULL );
... but this here is trying to get the Aldebaran PCI device function.
So what happens if in the future, the GPU is a different one and it
gets RAS functionality and PCI device functions too? You'd probably need to add that new GPU support too.
And then looking at that patch again, see how this new code is bolted on and sure, it all is made to work, but it is strenuous and you have to always pay attention to what type of devices you're dealing with.
And the next patch does:
... if (bank_type == SMCA_UMC_V2) {
/* do UMC v2 special stuff here. */which begs the question: wouldn't this GPU PCI devices enumeration be a lot cleaner if it were separate?
I.e., in amd_nb.c you'd have
init_amd_nbs:
amd_cache_northbridges();
amd_cache_gart();
amd_cache_gpu_devices();and in this last one you do your enumeration. Completely separate data structures and all. Adding a new device support would then be trivial.
And then looking at the next patch again, you have:
+ } else if (bank_type == SMCA_UMC_V2) {
+ /*
+ * SMCA_UMC_V2 exists on GPU nodes, extract the node id
+ * from register MCA_IPID[47:44](InstanceIdHi).
+ * The InstanceIdHi field represents the instance ID of the GPU.
+ * Which needs to be mapped to a value used by Linux,
+ * where GPU nodes are simply numerically after the CPU nodes.
+ */
+ node_id = ((m->ipid >> 44) & 0xF) -
+ amd_gpu_node_start_id() + amd_cpu_node_count();
where instead of exporting those functions and having the caller do the calculations, you'd have a function in amd_nb.c which is called
amd_get_gpu_node_id(unsigned long ipid)
which will use those separate data structures mentioned above and give you the node id.
And those GPU node IDs are placed numerically after the CPU nodes so your code doesn't need to do anything special - just read out registers and cache them.
And you don't need those exports either - it is all nicely encapsulated and a single function is used to get the callers what they wanna know.
Hmmm?
Signature · 4 lines
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquetteRe: [PATCH v6 1/5] x86/amd_nb: Add support for northbridges on Aldebaran
Hi Boris,
Quoted 5 lines · Borislav Petkov
[CAUTION: External Email]
On Thu, Oct 28, 2021 at 06:31:02PM +0530, Naveen Krishna Chatradhi wrote:
Staring at this more...
Thanks for taking the time.
Quoted 14 lines
arch/x86/kernel/amd_nb.c struct amd_northbridge *node_to_amd_nb(int node) · line 169
Quoted 12 lines
arch/x86/kernel/amd_nb.c +11
-0+/* +* Newer AMD CPUs and GPUs whose data fabrics can be connected via custom xGMI +* links, comes with registers to gather local and remote node type map info. +* +* "Local Node Type" refers to nodes with the same type as that from which the +* register is read, and "Remote Node Type" refers to nodes with a different type. +* +* This function, reads the registers from GPU DF function 1. +* Hence, local nodes are GPU and remote nodes are CPUs. +*/ +static int amd_get_node_map (void )... so this is a generic function name...
Quoted 8 lines
arch/x86/kernel/amd_nb.c struct amd_northbridge *node_to_amd_nb(int node) · line 176
Quoted 7 lines
arch/x86/kernel/amd_nb.c +7
-0+{ +struct amd_node_map *nodemap; +struct pci_dev *pdev; +u32 tmp; + + pdev =pci_get_device (PCI_VENDOR_ID_AMD , +PCI_DEVICE_ID_AMD_ALDEBARAN_DF_F1 ,NULL );... but this here is trying to get the Aldebaran PCI device function.
I know, this is confusion. we will try to give a meaning for definition here.
Quoted 4 lines
So what happens if in the future, the GPU is a different one and it
gets RAS functionality and PCI device functions too? You'd probably need to add that new GPU support too.
Yes, might happen
Quoted 14 lines
And then looking at that patch again, see how this new code is bolted on and sure, it all is made to work, but it is strenuous and you have to always pay attention to what type of devices you're dealing with.
And the next patch does:
... if (bank_type == SMCA_UMC_V2) { /* do UMC v2 special stuff here. */which begs the question: wouldn't this GPU PCI devices enumeration be a lot cleaner if it were separate?
Quoted 7 lines
I.e., in
amd_nb.cyou'd have
init_amd_nbs:amd_cache_northbridges(); amd_cache_gart(); amd_cache_gpu_devices();
Agreed. however, a slight modification to the suggestion
Instead of modifying the init_amd_nbs()
How about, defining a new struct
+struct system_topology {
+ const struct pci_device_id *misc_ids;
+ const struct pci_device_id *link_ids;
+ const struct pci_device_id *root_ids;
+ u16 roots_per_misc;
+ u16 misc_count;
+ u16 root_count;
+};
and modifying the amd_cache_northbridges() to
+int amd_cache_northbridges(void)
+{
+ struct system_toplogy topo;
+ int ret;
+
+ if (amd_northbridges.num)
+ return 0;
+
+ ret = amd_cpu_nbs(&topo);
+ printk("==> misc:%d\n", ret);
+
+ if (look_for_remote_nodes()) {
+ ret = amd_gpu_nbs(&topo); + printk("==> gpu_misc:%d\n", ret); + }
+
+ get_next_northbridges(&topo);
This way, creating appropriate number MCs under EDAC and existing exported APIs can remain the same.
Let me know your thoughts on this. I can send an updated version with your comments addressed.
Quoted 17 lines
and in this last one you do your enumeration. Completely separate data structures and all. Adding a new device support would then be trivial.
And then looking at the next patch again, you have:
(quoted diff) +10
-0+ } else if (bank_type == SMCA_UMC_V2) { + /* + * SMCA_UMC_V2 exists on GPU nodes, extract the node id + * from register MCA_IPID[47:44](InstanceIdHi). + * The InstanceIdHi field represents the instance ID of the GPU. + * Which needs to be mapped to a value used by Linux, + * where GPU nodes are simply numerically after the CPU nodes. + */ + node_id = ((m->ipid >> 44) & 0xF) - + amd_gpu_node_start_id() + amd_cpu_node_count();
Quoted 7 lines
where instead of exporting those functions and having the caller do the calculations, you'd have a function in
amd_nb.cwhich is called
amd_get_gpu_node_id(unsigned long ipid)which will use those separate data structures mentioned above and give you the node id.
Sure, we can modify this way.
Quoted 7 lines
And those GPU node IDs are placed numerically after the CPU nodes so your code doesn't need to do anything special - just read out registers and cache them.
And you don't need those exports either - it is all nicely encapsulated and a single function is used to get the callers what they wanna know.
Got it, thank you.
Borislav Petkov
maintainerRe: [PATCH v6 1/5] x86/amd_nb: Add support for northbridges on Aldebaran
Quoted 2 lines · Naveen Krishna
I know, this is confusion. we will try to give a meaning for definition here.
Well, not that - you will need to keep adding PCI device IDs for the future GPUs supporting this stuff.
Review
Quoted 10 lines
How about, defining a new struct
(quoted diff) +8
-0+struct system_topology { + const struct pci_device_id *misc_ids; + const struct pci_device_id *link_ids; + const struct pci_device_id *root_ids; + u16 roots_per_misc; + u16 misc_count; + u16 root_count; +};
Well, how does having a single struct help make things easier?
IOW, if you use accessors to get the information you need, it doesn't really matter what the underlying organization of the data is. And if it helps to keep 'em separate because stuff is simple altogether, then, they should be separate.
So, before you ask "How about", think of answering the question "Why should it be done this way? What are the advantages?"
Quoted 2 lines
This way, creating appropriate number MCs under EDAC and existing exported APIs can remain the same.
Why does that matter?
Also, have you verified in what order the init_amd_nbs() fs initcall and amd64_edac_init() get executed?
I'm going to venture a pretty sure guess that the initcall runs first and that amd_cache_northbridges() call in amd64_edac_init() is probably not even needed anymore...
Thx.
Signature · 4 lines
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquetteRe: [PATCH v6 1/5] x86/amd_nb: Add support for northbridges on Aldebaran
Hi Boris,
Quoted 7 lines · Borislav Petkov
[CAUTION: External Email]
Quoted 2 lines · Naveen Krishna
I know, this is confusion. we will try to give a meaning for definition here.
Well, not that - you will need to keep adding PCI device IDs for the future GPUs supporting this stuff.
Creating a pci_device_id list for GPUs will be needed.
Quoted 12 lines
Review
Quoted 11 lines
How about, defining a new struct
(quoted diff) +8
-0+struct system_topology { + const struct pci_device_id *misc_ids; + const struct pci_device_id *link_ids; + const struct pci_device_id *root_ids; + u16 roots_per_misc; + u16 misc_count; + u16 root_count; +};Well, how does having a single struct help make things easier?
Northbridges on CPUs and GPUs can be described using the elements in the above structure.
Quoted 5 lines
IOW, if you use accessors to get the information you need, it doesn't really matter what the underlying organization of the data is. And if it helps to keep 'em separate because stuff is simple altogether, then, they should be separate.
I thought organizing the data in a structure would simplify the initialization of cpus and gpus.
Quoted 3 lines
So, before you ask "How about", think of answering the question "Why should it be done this way? What are the advantages?"
I will modify the patch to enumerate gpu northbridge info only if there are
gpu nodes with pci_device to access the node_map registers.
Quoted 11 lines
Quoted 3 lines
This way, creating appropriate number MCs under EDAC and existing exported APIs can remain the same.
Why does that matter?
Also, have you verified in what order the
init_amd_nbs()fs initcall andamd64_edac_init()get executed?I'm going to venture a pretty sure guess that the initcall runs first and that
amd_cache_northbridges()call inamd64_edac_init()is probably not even needed anymore...
Yes, fs_initcall come before module_init (which inturn is device_init level 6). We can replace the amd_cache_northbridges() call in amd64_edac_init() with if(amd_nb_num() < 0).
Borislav Petkov
maintainerRe: [PATCH v6 1/5] x86/amd_nb: Add support for northbridges on Aldebaran
Quoted 2 lines · Naveen Krishna
Northbridges on CPUs and GPUs can be described using the elements in the above structure.
If you're going to describe *northbridges*, then your struct cannot be called system_topology...
Quoted 2 lines
I thought organizing the data in a structure would simplify the initialization of cpus and gpus.
Ehh, did you even read my mail where I tried to explain that sprinkling
if (gpu)
this
else
that
all over amd_cache_northbridges() is not proper design?
;-\
Quoted 3 lines
I will modify the patch to enumerate gpu northbridge info only if there are
gpu nodes with
pci_deviceto access thenode_mapregisters.
Why would you do that? What's the advantage?
How about you answer my questions first so that we agree on the design first before you go and do things?
Hmm.
Signature · 4 lines
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquetteRe: [PATCH v6 1/5] x86/amd_nb: Add support for northbridges on Aldebaran
Hi Boris,
Quoted 21 lines · Borislav Petkov
[CAUTION: External Email]
Quoted 2 lines · Naveen Krishna
Northbridges on CPUs and GPUs can be described using the elements in the above structure.
If you're going to describe *northbridges*, then your struct cannot be called
system_topology...Quoted 2 lines
I thought organizing the data in a structure would simplify the initialization of cpus and gpus.
Ehh, did you even read my mail where I tried to explain that sprinkling
if (gpu)
this
else
thatall over
amd_cache_northbridges()is not proper design?;-\
Quoted 7 lines
Quoted 3 lines
I will modify the patch to enumerate gpu northbridge info only if there are
gpu nodes with
pci_deviceto access thenode_mapregisters.Why would you do that? What's the advantage?
How about you answer my questions first so that we agree on the design first before you go and do things?
I was trying to handle both cpu and cpu northbridge enumeration in the amd_cache_northbridges() itself by reusing the existing structures and APIs.
Should have seen this through more clearly. As, this is working well for the following reasons.
a. Allocating the amd_northbridges.nb after identifying both the cpu and gpu misc devices, would extend node_to_amd_nb(node) for both cpu and gpu nodes.
It is used extensively in this module. However, the roots_per_misc value is different in case of cpus and gpus and that needed to be handled seperately.
b. amd_nb_num(void) is used by other modules in the kernel, returning the total count of CPU and GPU northbridges would break the existing code.
I understood your point now.
When we create separate functions for caching cpu and gpu devices, is it okay to create "struct amd_gpu_nb_info" with the following fields
a. gpu_num;
b. struct amd_northbridge *gpu_nb;
c. gpu_node_start_id;
While, amd_nb_num(), continues to return number of cpu NBs Add new API amd_gpu_nb_num(), return number of gpu NBs
and modify the node_to_amd_nb(node) to extend the same behavior for gpu devices also
Regards,
naveenk
Borislav Petkov
maintainerRe: [PATCH v6 1/5] x86/amd_nb: Add support for northbridges on Aldebaran
Quoted 5 lines · Naveen Krishna
I was trying to handle both cpu and cpu northbridge enumeration in the
amd_cache_northbridges()itself by reusing the existing structures and APIs.Should have seen this through more clearly. As, this is working well for the following reasons.
Good, that's exactly what I meant! :)
Quoted 2 lines
a. Allocating the amd_northbridges.nb after identifying both the cpu and gpu misc devices, would extend
node_to_amd_nb(node)for both cpu and gpu nodes.
Well, there's a reason those things are functions - so that you can do the necessary computation inside them and when stuff needs to change, users don't have to. That's why amd_northbridges is static and only the functions are exported.
So if you want to make sure node_to_amd_nb() works for GPU nodes too, you simply have to look at the right "container" so to speak, depending on the number @node passed in as an argument and look it up in the proper array of pointers:
[ CPU_NB0, CPU_NB1, ..., CPU_NB-N] [ GPU_NB0, ... ]
you get the idea.
Quoted 6 lines
It is used extensively in this module. However, the
roots_per_miscvalue is different in case of cpus and gpus and that needed to be handled seperately.b.
amd_nb_num(void)is used by other modules in the kernel, returning the total count of CPU and GPU northbridges would break the existing code.
amd64_edac is using it too, to know how many driver instances to allocate.
The other users - amd_gart_64.c and amd64-agp.c - are old stuff so they most certainly don't need to get the number of GPU nodes too.
Quoted 1 line
I understood your point now.
Good.
Quoted 6 lines
When we create separate functions for caching cpu and gpu devices, is it okay to create "struct
amd_gpu_nb_info" with the following fieldsa.
gpu_num;
b. structamd_northbridge*gpu_nb;
c.gpu_node_start_id;
Makes sense. You need to put in it anything that describes the GPU NBs on the system and that other code would use.
Quoted 5 lines
While,
amd_nb_num(), continues to return number of cpu NBs Add new APIamd_gpu_nb_num(), return number of gpu NBsand modify the
node_to_amd_nb(node)to extend the same behavior for gpu devices also
Yap, exactly.
And since amd64_edac is going to need the full NB count, you can use there both:
num_nodes = amd_nb_num() + amd_gpu_nb_num(); ...
Easy, peasy. :-)
Thanks!
Signature · 4 lines
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquetteRe: [PATCH v6 1/5] x86/amd_nb: Add support for northbridges on Aldebaran
In reply to Borislav PetkovHi Boris,
Quoted 5 lines · Borislav Petkov
[CAUTION: External Email]
On Thu, Oct 28, 2021 at 06:31:02PM +0530, Naveen Krishna Chatradhi wrote:
Staring at this more...
Thanks for taking the time.
Quoted 12 lines
arch/x86/kernel/amd_nb.c struct amd_northbridge *node_to_amd_nb(int node) · line 169
Quoted 11 lines
arch/x86/kernel/amd_nb.c +11
-0+/* +* Newer AMD CPUs and GPUs whose data fabrics can be connected via custom xGMI +* links, comes with registers to gather local and remote node type map info. +* +* "Local Node Type" refers to nodes with the same type as that from which the +* register is read, and "Remote Node Type" refers to nodes with a different type. +* +* This function, reads the registers from GPU DF function 1. +* Hence, local nodes are GPU and remote nodes are CPUs. +*/ +static int amd_get_node_map (void )... so this is a generic function name...
Quoted 8 lines
arch/x86/kernel/amd_nb.c struct amd_northbridge *node_to_amd_nb(int node) · line 176
Quoted 7 lines
arch/x86/kernel/amd_nb.c +7
-0+{ +struct amd_node_map *nodemap; +struct pci_dev *pdev; +u32 tmp; + + pdev =pci_get_device (PCI_VENDOR_ID_AMD , +PCI_DEVICE_ID_AMD_ALDEBARAN_DF_F1 ,NULL );... but this here is trying to get the Aldebaran PCI device function.
I know, this is confusion. we will try to give a meaning for definition here.
Quoted 3 lines
So what happens if in the future, the GPU is a different one and it
gets RAS functionality and PCI device functions too? You'd probably need to add that new GPU support too.
Yes, might happen
Quoted 13 lines
And then looking at that patch again, see how this new code is bolted on and sure, it all is made to work, but it is strenuous and you have to always pay attention to what type of devices you're dealing with.
And the next patch does:
... if (bank_type == SMCA_UMC_V2) { /* do UMC v2 special stuff here. */which begs the question: wouldn't this GPU PCI devices enumeration be a lot cleaner if it were separate?
Quoted 7 lines
I.e., in
amd_nb.cyou'd have
init_amd_nbs:amd_cache_northbridges(); amd_cache_gart(); amd_cache_gpu_devices();
Agreed. however, a slight modification to the suggestion
Instead of modiying the init_amd_nbs()
How about, modifying the amd_cache_northbridges() to
define a
call amd_prep_cpu_nbs()
Quoted 38 lines
and in this last one you do your enumeration. Completely separate data structures and all. Adding a new device support would then be trivial.
And then looking at the next patch again, you have:
(quoted diff) +10
-0+ } else if (bank_type == SMCA_UMC_V2) { + /* + * SMCA_UMC_V2 exists on GPU nodes, extract the node id + * from register MCA_IPID[47:44](InstanceIdHi). + * The InstanceIdHi field represents the instance ID of the GPU. + * Which needs to be mapped to a value used by Linux, + * where GPU nodes are simply numerically after the CPU nodes. + */ + node_id = ((m->ipid >> 44) & 0xF) - + amd_gpu_node_start_id() + amd_cpu_node_count();where instead of exporting those functions and having the caller do the calculations, you'd have a function in
amd_nb.cwhich is called
amd_get_gpu_node_id(unsigned long ipid)which will use those separate data structures mentioned above and give you the node id.
And those GPU node IDs are placed numerically after the CPU nodes so your code doesn't need to do anything special - just read out registers and cache them.
And you don't need those exports either - it is all nicely encapsulated and a single function is used to get the callers what they wanna know.
Hmmm?
--
Regards/Gruss,
Boris.
PATCH v6 2/5 EDAC/mce_amd: Extract node id from MCA_IPID
In reply to Naveen Krishna ChatradhiOn SMCA banks of the GPU nodes, the node id information is available in register MCA_IPID[47:44](InstanceIdHi).
Convert the hardware node ID to a value used by Linux where GPU nodes are sequencially after the CPU nodes.
---
Changes since v5:
None
Changes since v4:
Add reviewed by Yazen
Changes since v3:
1. Use APIs from amd_nb to identify the gpu_node_start_id and cpu_node_count. Which is required to map the hardware node id to node id enumerated by Linux.
Changes since v2:
1. Modified subject and commit message
2. Added Reviewed by Yazen Ghannam
Changes since v1:
1. Modified the commit message
2. rearranged the conditions before calling decode_dram_ecc()
drivers/edac/mce_amd.c | 24 ++++++++++++++++++++++-- 1 file changed, 22 insertions(+), 2 deletions(-)
drivers/edac/mce_amd.c +22 -2
@@ -2,6 +2,7 @@#include <linux/module.h> #include <linux/slab.h> +#include <asm/amd_nb.h> #include <asm/cpu.h> #include "mce_amd.h"
@@ -1072,8 +1073,27 @@ static void decode_smca_error(struct mce *m)if (xec < smca_mce_descs[bank_type].num_descs)pr_cont (", %s.\n" , smca_mce_descs[bank_type].descs[xec]); -if (bank_type ==SMCA_UMC && xec ==0 && decode_dram_ecc) -decode_dram_ecc (topology_die_id (m->extcpu), m); +if (xec ==0 && decode_dram_ecc) { +int node_id =0 ; + +if (bank_type ==SMCA_UMC ) { + node_id =topology_die_id (m->extcpu); + }else if (bank_type ==SMCA_UMC_V2 ) { +/* +* SMCA_UMC_V2 exists on GPU nodes, extract the node id +* from register MCA_IPID[47:44](InstanceIdHi). +* The InstanceIdHi field represents the instance ID of the GPU. +* Which needs to be mapped to a value used by Linux, +* where GPU nodes are simply numerically after the CPU nodes. +*/ + node_id = ((m->ipid >>44 ) &0xF ) - +amd_gpu_node_start_id () +amd_cpu_node_count (); + }else { +return ; + } + +decode_dram_ecc (node_id, m); + } }static inline void amd_decode_err_code (u16 ec)
Signature · 1 line
2.25.1
Borislav Petkov
maintainerRe: [PATCH v6 2/5] EDAC/mce_amd: Extract node id from MCA_IPID
Quoted 5 lines · Naveen Krishna Chatradhi
On SMCA banks of the GPU nodes, the node id information is available in register MCA_IPID[47:44](InstanceIdHi).
Convert the hardware node ID to a value used by Linux where GPU nodes are sequencially after the CPU nodes.
"sequentially"
Use a spellchecker when writing commit messages pls.
Signature · 4 lines
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquettePATCH v6 3/5 EDAC/amd64: Extend family ops functions
In reply to Naveen Krishna ChatradhiFrom: Muralidhara M K <[email protected]>
Create new family operation routines and define them respectively. This would simplify adding support for future platforms.
---
Changes since v5:
split read_mc_regs for per family ops
Adjusted and Called dump_misc_regs for family ops
Changes since v4:
1. Modified k8_prep_chip_selects for ext_model checks
2. Add read_dct_base_mask to ops
3. Renamed find_umc_channel and addressed minor comments
Changes since v3:
1. Defined new family operation routines
Changs since v2:
1. new patch
drivers/edac/amd64_edac.c | 302 +++++++++++++++++++++++--------------- drivers/edac/amd64_edac.h | 10 +- 2 files changed, 188 insertions(+), 124 deletions(-)
drivers/edac/amd64_edac.c +180 -122
@@ -1204,10 +1204,7 @@ static void __dump_misc_regs(struct amd64_pvt *pvt)/* Display and decode various NB registers for debug purposes. */ static void dump_misc_regs (struct amd64_pvt *pvt) { -if (pvt->umc) -__dump_misc_regs_df (pvt); -else -__dump_misc_regs (pvt); + pvt->ops->get_misc_regs (pvt);edac_dbg (1 ," DramHoleValid: %s\n" ,dhar_valid (pvt) ?"yes" :"no" );
@@ -1217,28 +1214,39 @@ static void dump_misc_regs(struct amd64_pvt *pvt)/* * See BKDG, F2x[1,0][5C:40], F2[1,0][6C:60] */ -static void prep_chip_selects (struct amd64_pvt *pvt) +static void k8_prep_chip_selects (struct amd64_pvt *pvt) {if (pvt->fam ==0xf && pvt->ext_model <K8_REV_F ) { pvt->csels[0 ].b_cnt = pvt->csels[1 ].b_cnt =8 ; pvt->csels[0 ].m_cnt = pvt->csels[1 ].m_cnt =8 ; - }else if (pvt->fam ==0x15 && pvt->model ==0x30 ) { - pvt->csels[0 ].b_cnt = pvt->csels[1 ].b_cnt =4 ; - pvt->csels[0 ].m_cnt = pvt->csels[1 ].m_cnt =2 ; - }else if (pvt->fam >=0x17 ) { -int umc; - -for_each_umc (umc) { - pvt->csels[umc].b_cnt =4 ; - pvt->csels[umc].m_cnt =2 ; - } - - }else { + }else if (pvt->fam ==0xf && pvt->ext_model >=K8_REV_F ) { pvt->csels[0 ].b_cnt = pvt->csels[1 ].b_cnt =8 ; pvt->csels[0 ].m_cnt = pvt->csels[1 ].m_cnt =4 ; } } +static void f15m30_prep_chip_selects (struct amd64_pvt *pvt) +{ + pvt->csels[0 ].b_cnt = pvt->csels[1 ].b_cnt =4 ; + pvt->csels[0 ].m_cnt = pvt->csels[1 ].m_cnt =2 ; +} + +static void default_prep_chip_selects (struct amd64_pvt *pvt) +{ + pvt->csels[0 ].b_cnt = pvt->csels[1 ].b_cnt =8 ; + pvt->csels[0 ].m_cnt = pvt->csels[1 ].m_cnt =4 ; +} + +static void f17_prep_chip_selects (struct amd64_pvt *pvt) +{ +int umc; + +for_each_umc (umc) { + pvt->csels[umc].b_cnt =4 ; + pvt->csels[umc].m_cnt =2 ; + } +} +static void read_umc_base_mask (struct amd64_pvt *pvt) {u32 umc_base_reg, umc_base_reg_sec;
@@ -1297,11 +1305,6 @@ static void read_dct_base_mask(struct amd64_pvt *pvt) {int cs; -prep_chip_selects (pvt); - -if (pvt->umc) -return read_umc_base_mask (pvt); -for_each_chip_select (cs,0 , pvt) {int reg0 =DCSB0 + (cs *4 );int reg1 =DCSB1 + (cs *4 );
@@ -2512,143 +2515,181 @@ static void debug_display_dimm_sizes(struct amd64_pvt *pvt, u8 ctrl) } } +/* Prototypes for family specific ops routines */ +static int init_csrows (struct mem_ctl_info *mci); +static int init_csrows_df (struct mem_ctl_info *mci); +static void read_mc_regs (struct amd64_pvt *pvt); +static void __read_mc_regs_df (struct amd64_pvt *pvt); +static void update_umc_err_info (struct mce *m,struct err_info *err); + +static const struct low_ops k8_ops = { + .early_channel_count = k8_early_channel_count, + .map_sysaddr_to_csrow = k8_map_sysaddr_to_csrow, + .dbam_to_cs = k8_dbam_to_chip_select, + .prep_chip_select = k8_prep_chip_selects, + .get_base_mask = read_dct_base_mask, + .get_misc_regs = __dump_misc_regs, + .get_mc_regs = read_mc_regs, + .populate_csrows = init_csrows, +}; + +static const struct low_ops f10_ops = { + .early_channel_count = f1x_early_channel_count, + .map_sysaddr_to_csrow = f1x_map_sysaddr_to_csrow, + .dbam_to_cs = f10_dbam_to_chip_select, + .prep_chip_select = default_prep_chip_selects, + .get_base_mask = read_dct_base_mask, + .get_misc_regs = __dump_misc_regs, + .get_mc_regs = read_mc_regs, + .populate_csrows = init_csrows, +}; + +static const struct low_ops f15_ops = { + .early_channel_count = f1x_early_channel_count, + .map_sysaddr_to_csrow = f1x_map_sysaddr_to_csrow, + .dbam_to_cs = f15_dbam_to_chip_select, + .prep_chip_select = default_prep_chip_selects, + .get_base_mask = read_dct_base_mask, + .get_misc_regs = __dump_misc_regs, + .get_mc_regs = read_mc_regs, + .populate_csrows = init_csrows, +}; + +static const struct low_ops f15m30_ops = { + .early_channel_count = f1x_early_channel_count, + .map_sysaddr_to_csrow = f1x_map_sysaddr_to_csrow, + .dbam_to_cs = f16_dbam_to_chip_select, + .prep_chip_select = f15m30_prep_chip_selects, + .get_base_mask = read_dct_base_mask, + .get_misc_regs = __dump_misc_regs, + .get_mc_regs = read_mc_regs, + .populate_csrows = init_csrows, +}; + +static const struct low_ops f15m60_ops = { + .early_channel_count = f1x_early_channel_count, + .map_sysaddr_to_csrow = f1x_map_sysaddr_to_csrow, + .dbam_to_cs = f15_m60h_dbam_to_chip_select, + .prep_chip_select = default_prep_chip_selects, + .get_base_mask = read_dct_base_mask, + .get_misc_regs = __dump_misc_regs, + .get_mc_regs = read_mc_regs, + .populate_csrows = init_csrows, +}; + +static const struct low_ops f16_ops = { + .early_channel_count = f1x_early_channel_count, + .map_sysaddr_to_csrow = f1x_map_sysaddr_to_csrow, + .dbam_to_cs = f16_dbam_to_chip_select, + .prep_chip_select = default_prep_chip_selects, + .get_base_mask = read_dct_base_mask, + .get_misc_regs = __dump_misc_regs, + .get_mc_regs = read_mc_regs, + .populate_csrows = init_csrows, +}; + +static const struct low_ops f17_ops = { + .early_channel_count = f17_early_channel_count, + .dbam_to_cs = f17_addr_mask_to_cs_size, + .prep_chip_select = f17_prep_chip_selects, + .get_base_mask = read_umc_base_mask, + .get_misc_regs = __dump_misc_regs_df, + .get_mc_regs = __read_mc_regs_df, + .populate_csrows = init_csrows_df, + .get_umc_err_info = update_umc_err_info, +}; +static struct amd64_family_type family_types[] = { [K8_CPUS ] = { .ctl_name ="K8" , .f1_id =PCI_DEVICE_ID_AMD_K8_NB_ADDRMAP , .f2_id =PCI_DEVICE_ID_AMD_K8_NB_MEMCTL , .max_mcs =2 , - .ops = { - .early_channel_count = k8_early_channel_count, - .map_sysaddr_to_csrow = k8_map_sysaddr_to_csrow, - .dbam_to_cs = k8_dbam_to_chip_select, - } + .ops = k8_ops, }, [F10_CPUS ] = { .ctl_name ="F10h" , .f1_id =PCI_DEVICE_ID_AMD_10H_NB_MAP , .f2_id =PCI_DEVICE_ID_AMD_10H_NB_DRAM , .max_mcs =2 , - .ops = { - .early_channel_count = f1x_early_channel_count, - .map_sysaddr_to_csrow = f1x_map_sysaddr_to_csrow, - .dbam_to_cs = f10_dbam_to_chip_select, - } + .ops = f10_ops, }, [F15_CPUS ] = { .ctl_name ="F15h" , .f1_id =PCI_DEVICE_ID_AMD_15H_NB_F1 , .f2_id =PCI_DEVICE_ID_AMD_15H_NB_F2 , .max_mcs =2 , - .ops = { - .early_channel_count = f1x_early_channel_count, - .map_sysaddr_to_csrow = f1x_map_sysaddr_to_csrow, - .dbam_to_cs = f15_dbam_to_chip_select, - } + .ops = f15_ops, }, [F15_M30H_CPUS ] = { .ctl_name ="F15h_M30h" , .f1_id =PCI_DEVICE_ID_AMD_15H_M30H_NB_F1 , .f2_id =PCI_DEVICE_ID_AMD_15H_M30H_NB_F2 , .max_mcs =2 , - .ops = { - .early_channel_count = f1x_early_channel_count, - .map_sysaddr_to_csrow = f1x_map_sysaddr_to_csrow, - .dbam_to_cs = f16_dbam_to_chip_select, - } + .ops = f15m30_ops, }, [F15_M60H_CPUS ] = { .ctl_name ="F15h_M60h" , .f1_id =PCI_DEVICE_ID_AMD_15H_M60H_NB_F1 , .f2_id =PCI_DEVICE_ID_AMD_15H_M60H_NB_F2 , .max_mcs =2 , - .ops = { - .early_channel_count = f1x_early_channel_count, - .map_sysaddr_to_csrow = f1x_map_sysaddr_to_csrow, - .dbam_to_cs = f15_m60h_dbam_to_chip_select, - } + .ops = f15m60_ops, }, [F16_CPUS ] = { .ctl_name ="F16h" , .f1_id =PCI_DEVICE_ID_AMD_16H_NB_F1 , .f2_id =PCI_DEVICE_ID_AMD_16H_NB_F2 , .max_mcs =2 , - .ops = { - .early_channel_count = f1x_early_channel_count, - .map_sysaddr_to_csrow = f1x_map_sysaddr_to_csrow, - .dbam_to_cs = f16_dbam_to_chip_select, - } + .ops = f16_ops, }, [F16_M30H_CPUS ] = { .ctl_name ="F16h_M30h" , .f1_id =PCI_DEVICE_ID_AMD_16H_M30H_NB_F1 , .f2_id =PCI_DEVICE_ID_AMD_16H_M30H_NB_F2 , .max_mcs =2 , - .ops = { - .early_channel_count = f1x_early_channel_count, - .map_sysaddr_to_csrow = f1x_map_sysaddr_to_csrow, - .dbam_to_cs = f16_dbam_to_chip_select, - } + .ops = f16_ops, }, [F17_CPUS ] = { .ctl_name ="F17h" , .f0_id =PCI_DEVICE_ID_AMD_17H_DF_F0 , .f6_id =PCI_DEVICE_ID_AMD_17H_DF_F6 , .max_mcs =2 , - .ops = { - .early_channel_count = f17_early_channel_count, - .dbam_to_cs = f17_addr_mask_to_cs_size, - } + .ops = f17_ops, }, [F17_M10H_CPUS ] = { .ctl_name ="F17h_M10h" , .f0_id =PCI_DEVICE_ID_AMD_17H_M10H_DF_F0 , .f6_id =PCI_DEVICE_ID_AMD_17H_M10H_DF_F6 , .max_mcs =2 , - .ops = { - .early_channel_count = f17_early_channel_count, - .dbam_to_cs = f17_addr_mask_to_cs_size, - } + .ops = f17_ops, }, [F17_M30H_CPUS ] = { .ctl_name ="F17h_M30h" , .f0_id =PCI_DEVICE_ID_AMD_17H_M30H_DF_F0 , .f6_id =PCI_DEVICE_ID_AMD_17H_M30H_DF_F6 , .max_mcs =8 , - .ops = { - .early_channel_count = f17_early_channel_count, - .dbam_to_cs = f17_addr_mask_to_cs_size, - } + .ops = f17_ops, }, [F17_M60H_CPUS ] = { .ctl_name ="F17h_M60h" , .f0_id =PCI_DEVICE_ID_AMD_17H_M60H_DF_F0 , .f6_id =PCI_DEVICE_ID_AMD_17H_M60H_DF_F6 , .max_mcs =2 , - .ops = { - .early_channel_count = f17_early_channel_count, - .dbam_to_cs = f17_addr_mask_to_cs_size, - } + .ops = f17_ops, }, [F17_M70H_CPUS ] = { .ctl_name ="F17h_M70h" , .f0_id =PCI_DEVICE_ID_AMD_17H_M70H_DF_F0 , .f6_id =PCI_DEVICE_ID_AMD_17H_M70H_DF_F6 , .max_mcs =2 , - .ops = { - .early_channel_count = f17_early_channel_count, - .dbam_to_cs = f17_addr_mask_to_cs_size, - } + .ops = f17_ops, }, [F19_CPUS ] = { .ctl_name ="F19h" , .f0_id =PCI_DEVICE_ID_AMD_19H_DF_F0 , .f6_id =PCI_DEVICE_ID_AMD_19H_DF_F6 , .max_mcs =8 , - .ops = { - .early_channel_count = f17_early_channel_count, - .dbam_to_cs = f17_addr_mask_to_cs_size, - } + .ops = f17_ops, }, };
@@ -2899,10 +2940,13 @@ static inline void decode_bus_error(int node_id, struct mce *m)* Currently, we can derive the channel number by looking at the 6th nibble in * the instance_id. For example, instance_id=0xYXXXXX where Y is the channel * number. +* +* csrow can be derived from the lower 3 bits of MCA_SYND value. */ -static int find_umc_channel (struct mce *m) +static void update_umc_err_info (struct mce *m,struct err_info *err) { -return (m->ipid &GENMASK (31 ,0 )) >>20 ; + err->channel = (m->ipid &GENMASK (31 ,0 )) >>20 ; + err->csrow = m->synd &0x7 ; }static void decode_umc_error (int node_id,struct mce *m)
@@ -2924,8 +2968,6 @@ static void decode_umc_error(int node_id, struct mce *m)if (m->status &MCI_STATUS_DEFERRED ) ecc_type =3 ; - err.channel =find_umc_channel (m); -if (!(m->status &MCI_STATUS_SYNDV )) { err.err_code =ERR_SYND ; goto log_error;
@@ -2940,7 +2982,7 @@ static void decode_umc_error(int node_id, struct mce *m) err.err_code =ERR_CHANNEL ; } - err.csrow = m->synd &0x7 ; + pvt->ops->get_umc_err_info (m, &err);if (umc_normaddr_to_sysaddr (m->addr, pvt->mc_node_id, err.channel, &sys_addr)) { err.err_code =ERR_NORM_ADDR ;
@@ -3058,6 +3100,27 @@ static void determine_ecc_sym_sz(struct amd64_pvt *pvt) } } +static void read_top_mem_registers (struct amd64_pvt *pvt) +{ +u64 msr_val; + +/* +* Retrieve TOP_MEM and TOP_MEM2; no masking off of reserved bits since +* those are Read-As-Zero. +*/ +rdmsrl (MSR_K8_TOP_MEM1 , pvt->top_mem); +edac_dbg (0 ," TOP_MEM: 0x%016llx\n" , pvt->top_mem); + +/* Check first whether TOP_MEM2 is enabled: */ +rdmsrl (MSR_AMD64_SYSCFG , msr_val); +if (msr_val &BIT (21 )) { +rdmsrl (MSR_K8_TOP_MEM2 , pvt->top_mem2); +edac_dbg (0 ," TOP_MEM2: 0x%016llx\n" , pvt->top_mem2); + }else { +edac_dbg (0 ," TOP_MEM2 disabled\n" ); + } +} +/* * Retrieve the hardware registers of the memory controller. */
@@ -3067,6 +3130,8 @@ static void __read_mc_regs_df(struct amd64_pvt *pvt)struct amd64_umc *umc;u32 i, umc_base; +read_top_mem_registers (pvt); +/* Read registers from each UMC */ for_each_umc (i) {
@@ -3079,6 +3144,8 @@ static void __read_mc_regs_df(struct amd64_pvt *pvt)amd_smn_read (nid, umc_base +UMCCH_ECC_CTRL , &umc->ecc_ctrl);amd_smn_read (nid, umc_base +UMCCH_UMC_CAP_HI , &umc->umc_cap_hi); } + +amd64_read_pci_cfg (pvt->F0,DF_DHAR , &pvt->dhar); }/*
@@ -3088,30 +3155,8 @@ static void __read_mc_regs_df(struct amd64_pvt *pvt)static void read_mc_regs (struct amd64_pvt *pvt) {unsigned int range; -u64 msr_val; - -/* -* Retrieve TOP_MEM and TOP_MEM2; no masking off of reserved bits since -* those are Read-As-Zero. -*/ -rdmsrl (MSR_K8_TOP_MEM1 , pvt->top_mem); -edac_dbg (0 ," TOP_MEM: 0x%016llx\n" , pvt->top_mem); - -/* Check first whether TOP_MEM2 is enabled: */ -rdmsrl (MSR_AMD64_SYSCFG , msr_val); -if (msr_val &BIT (21 )) { -rdmsrl (MSR_K8_TOP_MEM2 , pvt->top_mem2); -edac_dbg (0 ," TOP_MEM2: 0x%016llx\n" , pvt->top_mem2); - }else { -edac_dbg (0 ," TOP_MEM2 disabled\n" ); - } -if (pvt->umc) { -__read_mc_regs_df (pvt); -amd64_read_pci_cfg (pvt->F0,DF_DHAR , &pvt->dhar); - - goto skip; - } +read_top_mem_registers (pvt);amd64_read_pci_cfg (pvt->F3,NBCAP , &pvt->nbcap);
@@ -3152,14 +3197,6 @@ static void read_mc_regs(struct amd64_pvt *pvt)amd64_read_dct_pci_cfg (pvt,1 ,DCLR0 , &pvt->dclr1);amd64_read_dct_pci_cfg (pvt,1 ,DCHR0 , &pvt->dchr1); } - -skip: -read_dct_base_mask (pvt); - -determine_memory_type (pvt); -edac_dbg (1 ," DIMM type: %s\n" , edac_mem_types[pvt->dram_type]); - -determine_ecc_sym_sz (pvt); }/*
@@ -3277,9 +3314,6 @@ static int init_csrows(struct mem_ctl_info *mci)int nr_pages =0 ;u32 val; -if (pvt->umc) -return init_csrows_df (mci); -amd64_read_pci_cfg (pvt->F3,NBCFG , &val); pvt->nbcfg = val;
@@ -3703,6 +3737,21 @@ static struct amd64_family_type *per_family_init(struct amd64_pvt *pvt)return NULL ; } +/* ops required for all the families */ +if (!pvt->ops->early_channel_count || !pvt->ops->dbam_to_cs || + !pvt->ops->prep_chip_select || !pvt->ops->get_base_mask || + !pvt->ops->get_misc_regs || !pvt->ops->get_mc_regs || + !pvt->ops->populate_csrows) { +edac_dbg (1 ,"Common helper routines not defined.\n" ); +return NULL ; + } + +/* ops required for families 17h and later */ +if (pvt->fam >=0x17 && !pvt->ops->get_umc_err_info) { +edac_dbg (1 ,"Platform specific helper routines not defined.\n" ); +return NULL ; + } +return fam_type; }
@@ -3735,7 +3784,16 @@ static int hw_info_get(struct amd64_pvt *pvt)if (ret)return ret; -read_mc_regs (pvt); + pvt->ops->get_mc_regs (pvt); + + pvt->ops->prep_chip_select (pvt); + + pvt->ops->get_base_mask (pvt); + +determine_memory_type (pvt); +edac_dbg (1 ," DIMM type: %s\n" , edac_mem_types[pvt->dram_type]); + +determine_ecc_sym_sz (pvt);return 0 ; }
@@ -3786,7 +3844,7 @@ static int init_one_instance(struct amd64_pvt *pvt)setup_mci_misc_attrs (mci); -if (init_csrows (mci)) +if (pvt->ops->populate_csrows (mci)) mci->edac_cap =EDAC_FLAG_NONE ; ret = -ENODEV ;
drivers/edac/amd64_edac.h +8 -2
@@ -467,11 +467,17 @@ struct ecc_settings {* functions and per device encoding/decoding logic. */ struct low_ops { -int (*early_channel_count) (struct amd64_pvt *pvt); +int (*early_channel_count) (struct amd64_pvt *pvt);void (*map_sysaddr_to_csrow) (struct mem_ctl_info *mci,u64 sys_addr,struct err_info *); -int (*dbam_to_cs) (struct amd64_pvt *pvt,u8 dct, +int (*dbam_to_cs) (struct amd64_pvt *pvt,u8 dct,unsigned cs_mode,int cs_mask_nr); +void (*prep_chip_select) (struct amd64_pvt *pvt); +void (*get_base_mask) (struct amd64_pvt *pvt); +void (*get_misc_regs) (struct amd64_pvt *pvt); +void (*get_mc_regs) (struct amd64_pvt *pvt); +int (*populate_csrows) (struct mem_ctl_info *mci); +void (*get_umc_err_info) (struct mce *m,struct err_info *err); };struct amd64_family_type {
Signature · 1 line
2.25.1
Borislav Petkov
maintainerRe: [PATCH v6 3/5] EDAC/amd64: Extend family ops functions
Quoted 16 lines · Naveen Krishna Chatradhi
(quoted diff) +1
-7@@ -1217,28 +1214,39 @@ static void dump_misc_regs(struct amd64_pvt *pvt) /* * See BKDG, F2x[1,0][5C:40], F2[1,0][6C:60] */ -static void prep_chip_selects(struct amd64_pvt *pvt) +static void k8_prep_chip_selects(struct amd64_pvt *pvt) { if (pvt->fam == 0xf && pvt->ext_model < K8_REV_F) { pvt->csels[0].b_cnt = pvt->csels[1].b_cnt = 8; pvt->csels[0].m_cnt = pvt->csels[1].m_cnt = 8; - } else if (pvt->fam == 0x15 && pvt->model == 0x30) { - pvt->csels[0].b_cnt = pvt->csels[1].b_cnt = 4; - pvt->csels[0].m_cnt = pvt->csels[1].m_cnt = 2; - } else if (pvt->fam >= 0x17) { - int umc; -
Review static void dump_misc_regs(struct amd64_pvt *pvt) · line 1225
Quoted 10 lines
(quoted diff) +1
-6- for_each_umc(umc) { - pvt->csels[umc].b_cnt = 4; - pvt->csels[umc].m_cnt = 2; - } - - } else { + } else if (pvt->fam == 0xf && pvt->ext_model >= K8_REV_F) { pvt->csels[0].b_cnt = pvt->csels[1].b_cnt = 8; pvt->csels[0].m_cnt = pvt->csels[1].m_cnt = 4; }
Why is this function looking at the family if it is called a k8_... function which will be set only on K8?
Quoted 40 lines
(quoted diff) +22
-5} +static void f15m30_prep_chip_selects(struct amd64_pvt *pvt) +{ + pvt->csels[0].b_cnt = pvt->csels[1].b_cnt = 4; + pvt->csels[0].m_cnt = pvt->csels[1].m_cnt = 2; +} + +static void default_prep_chip_selects(struct amd64_pvt *pvt) +{ + pvt->csels[0].b_cnt = pvt->csels[1].b_cnt = 8; + pvt->csels[0].m_cnt = pvt->csels[1].m_cnt = 4; +} + +static void f17_prep_chip_selects(struct amd64_pvt *pvt) +{ + int umc; + + for_each_umc(umc) { + pvt->csels[umc].b_cnt = 4; + pvt->csels[umc].m_cnt = 2; + } +} + static void read_umc_base_mask(struct amd64_pvt *pvt) { u32 umc_base_reg, umc_base_reg_sec;@@ -1297,11 +1305,6 @@ static void read_dct_base_mask(struct amd64_pvt *pvt) { int cs; - prep_chip_selects(pvt); - - if (pvt->umc) - return read_umc_base_mask(pvt); - for_each_chip_select(cs, 0, pvt) { int reg0 = DCSB0 + (cs * 4); int reg1 = DCSB1 + (cs * 4);
Review static void debug_display_dimm_sizes(struct amd64_pvt *pvt, u8 ctrl) · line 2523
Quoted 9 lines
(quoted diff) +6
-0@@ -2512,143 +2515,181 @@ static void debug_display_dimm_sizes(struct amd64_pvt *pvt, u8 ctrl) } } +/* Prototypes for family specific ops routines */ +static int init_csrows(struct mem_ctl_info *mci); +static int init_csrows_df(struct mem_ctl_info *mci); +static void read_mc_regs(struct amd64_pvt *pvt); +static void __read_mc_regs_df(struct amd64_pvt *pvt); +static void update_umc_err_info(struct mce *m, struct err_info *err);
Prototypes belong in headers.
Review static void debug_display_dimm_sizes(struct amd64_pvt *pvt, u8 ctrl) · line 2525
Quoted 2 lines
(quoted diff) +2
-0+ +static const struct low_ops k8_ops = {
So if you're going to do this, you can go a step further and get rid of all those static definitions which are completely unused except those of the current family we're loaded on.
IOW, you should make all family-specific assignments dynamic and get rid of family_types and those ops. Here's an example I did for K8:
drivers/edac/amd64_edac.c +12 -2
@@ -3656,8 +3656,18 @@ static struct amd64_family_type *per_family_init(struct amd64_pvt *pvt)switch (pvt->fam) {case 0xf : - fam_type = &family_types[K8_CPUS ]; - pvt->ops = &family_types[K8_CPUS ].ops; + fam_type->ctl_name ="K8" ; + fam_type->f1_id =PCI_DEVICE_ID_AMD_K8_NB_ADDRMAP ; + fam_type->f2_id =PCI_DEVICE_ID_AMD_K8_NB_MEMCTL ; + fam_type->max_mcs =2 ; + pvt->ops->early_channel_count = k8_early_channel_count; + pvt->ops->map_sysaddr_to_csrow = k8_map_sysaddr_to_csrow; + pvt->ops->dbam_to_cs = k8_dbam_to_chip_select; + pvt->ops->prep_chip_select = k8_prep_chip_selects; + pvt->ops->get_base_mask = read_dct_base_mask; + pvt->ops->get_misc_regs = __dump_misc_regs; + pvt->ops->get_mc_regs = read_mc_regs; + pvt->ops->populate_csrows = init_csrows;break ;case 0x10 :
After that, pvt and fam_type have been properly set up.
Review static int hw_info_get(struct amd64_pvt *pvt) · line 3794
Quoted 13 lines
(quoted diff) +8
-1@@ -3735,7 +3784,16 @@ static int hw_info_get(struct amd64_pvt *pvt) if (ret) return ret; - read_mc_regs(pvt); + pvt->ops->get_mc_regs(pvt); + + pvt->ops->prep_chip_select(pvt); + + pvt->ops->get_base_mask(pvt); + + determine_memory_type(pvt); + edac_dbg(1, " DIMM type: %s\n", edac_mem_types[pvt->dram_type]);
Move that dbg call at the end of determine_memory_type().
Quoted 20 lines
(quoted diff) +3
-1+ + determine_ecc_sym_sz(pvt); return 0; }@@ -3786,7 +3844,7 @@ static int init_one_instance(struct amd64_pvt *pvt) setup_mci_misc_attrs(mci); - if (init_csrows(mci)) + if (pvt->ops->populate_csrows(mci)) mci->edac_cap = EDAC_FLAG_NONE; ret = -ENODEV;drivers/edac/amd64_edac.h +0
-0@@ -467,11 +467,17 @@ struct ecc_settings {* functions and per device encoding/decoding logic.
drivers/edac/amd64_edac.h struct ecc_settings { · line 475
Quoted 10 lines
drivers/edac/amd64_edac.h +3
-2*/ struct low_ops { -int (*early_channel_count) (struct amd64_pvt *pvt); +int (*early_channel_count) (struct amd64_pvt *pvt);void (*map_sysaddr_to_csrow) (struct mem_ctl_info *mci,u64 sys_addr,struct err_info *); -int (*dbam_to_cs) (struct amd64_pvt *pvt,u8 dct, +int (*dbam_to_cs) (struct amd64_pvt *pvt,u8 dct,unsigned cs_mode,int cs_mask_nr); +void (*prep_chip_select) (struct amd64_pvt *pvt);
That name should be "prep_chip_selects" - plural.
drivers/edac/amd64_edac.h struct ecc_settings { · line 480
Quoted 5 lines
drivers/edac/amd64_edac.h +5
-0+void (*get_base_mask) (struct amd64_pvt *pvt); +void (*get_misc_regs) (struct amd64_pvt *pvt); +void (*get_mc_regs) (struct amd64_pvt *pvt); +int (*populate_csrows) (struct mem_ctl_info *mci); +void (*get_umc_err_info) (struct mce *m,struct err_info *err);
WARNING: Unnecessary space before function pointer arguments #652: FILE: drivers/edac/amd64_edac.h:470:
+ int (*early_channel_count) (struct amd64_pvt *pvt);
WARNING: Unnecessary space before function pointer arguments #656: FILE: drivers/edac/amd64_edac.h:473:
+ int (*dbam_to_cs) (struct amd64_pvt *pvt, u8 dct,
WARNING: Unnecessary space before function pointer arguments #658: FILE: drivers/edac/amd64_edac.h:475:
+ void (*prep_chip_select) (struct amd64_pvt *pvt);
WARNING: Unnecessary space before function pointer arguments #659: FILE: drivers/edac/amd64_edac.h:476:
+ void (*get_base_mask) (struct amd64_pvt *pvt);
WARNING: Unnecessary space before function pointer arguments #660: FILE: drivers/edac/amd64_edac.h:477:
+ void (*get_misc_regs) (struct amd64_pvt *pvt);
WARNING: Unnecessary space before function pointer arguments #661: FILE: drivers/edac/amd64_edac.h:478:
+ void (*get_mc_regs) (struct amd64_pvt *pvt);
WARNING: Unnecessary space before function pointer arguments #662: FILE: drivers/edac/amd64_edac.h:479:
+ int (*populate_csrows) (struct mem_ctl_info *mci);
WARNING: Unnecessary space before function pointer arguments #663: FILE: drivers/edac/amd64_edac.h:480:
+ void (*get_umc_err_info) (struct mce *m, struct err_info *err);
total: 0 errors, 8 warnings, 507 lines checked
Please integrate scripts/checkpatch.pl into your patch creation workflow. Some of the warnings/errors *actually* make sense.
Signature · 4 lines
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquetteRe: [PATCH v6 3/5] EDAC/amd64: Extend family ops functions
Hi Boris
Quoted 23 lines · Borislav Petkov
[CAUTION: External Email]
Quoted 20 lines · Naveen Krishna Chatradhi
(quoted diff) +1
-11@@ -1217,28 +1214,39 @@ static void dump_misc_regs(struct amd64_pvt *pvt) /* * See BKDG, F2x[1,0][5C:40], F2[1,0][6C:60] */ -static void prep_chip_selects(struct amd64_pvt *pvt) +static void k8_prep_chip_selects(struct amd64_pvt *pvt) { if (pvt->fam == 0xf && pvt->ext_model < K8_REV_F) { pvt->csels[0].b_cnt = pvt->csels[1].b_cnt = 8; pvt->csels[0].m_cnt = pvt->csels[1].m_cnt = 8; - } else if (pvt->fam == 0x15 && pvt->model == 0x30) { - pvt->csels[0].b_cnt = pvt->csels[1].b_cnt = 4; - pvt->csels[0].m_cnt = pvt->csels[1].m_cnt = 2; - } else if (pvt->fam >= 0x17) { - int umc; - - for_each_umc(umc) { - pvt->csels[umc].b_cnt = 4; - pvt->csels[umc].m_cnt = 2; - }
Quoted 8 lines
Review static void dump_misc_regs(struct amd64_pvt *pvt) · line 1225
Quoted 6 lines
(quoted diff) +1
-2- - } else { + } else if (pvt->fam == 0xf && pvt->ext_model >= K8_REV_F) { pvt->csels[0].b_cnt = pvt->csels[1].b_cnt = 8; pvt->csels[0].m_cnt = pvt->csels[1].m_cnt = 4; }Why is this function looking at the family if it is called a
k8_... function which will be set only on K8?
Will modify.
Quoted 44 lines
Quoted 44 lines
(quoted diff) +22
-5} +static void f15m30_prep_chip_selects(struct amd64_pvt *pvt) +{ + pvt->csels[0].b_cnt = pvt->csels[1].b_cnt = 4; + pvt->csels[0].m_cnt = pvt->csels[1].m_cnt = 2; +} + +static void default_prep_chip_selects(struct amd64_pvt *pvt) +{ + pvt->csels[0].b_cnt = pvt->csels[1].b_cnt = 8; + pvt->csels[0].m_cnt = pvt->csels[1].m_cnt = 4; +} + +static void f17_prep_chip_selects(struct amd64_pvt *pvt) +{ + int umc; + + for_each_umc(umc) { + pvt->csels[umc].b_cnt = 4; + pvt->csels[umc].m_cnt = 2; + } +} + static void read_umc_base_mask(struct amd64_pvt *pvt) { u32 umc_base_reg, umc_base_reg_sec;@@ -1297,11 +1305,6 @@ static void read_dct_base_mask(struct amd64_pvt *pvt) { int cs; - prep_chip_selects(pvt); - - if (pvt->umc) - return read_umc_base_mask(pvt); - for_each_chip_select(cs, 0, pvt) { int reg0 = DCSB0 + (cs * 4); int reg1 = DCSB1 + (cs * 4);@@ -2512,143 +2515,181 @@ static void debug_display_dimm_sizes(struct amd64_pvt *pvt, u8 ctrl) } }
Quoted 7 lines
Review static void debug_display_dimm_sizes(struct amd64_pvt *pvt, u8 ctrl) · line 2523
Quoted 6 lines
(quoted diff) +6
-0+/* Prototypes for family specific ops routines */ +static int init_csrows(struct mem_ctl_info *mci); +static int init_csrows_df(struct mem_ctl_info *mci); +static void read_mc_regs(struct amd64_pvt *pvt); +static void __read_mc_regs_df(struct amd64_pvt *pvt); +static void update_umc_err_info(struct mce *m, struct err_info *err);Prototypes belong in headers.
Sure, this wont be necessary based on your other comments.
Quoted 36 lines
Review static void debug_display_dimm_sizes(struct amd64_pvt *pvt, u8 ctrl) · line 2525
Quoted 3 lines
(quoted diff) +2
-0+ +static const struct low_ops k8_ops = {So if you're going to do this, you can go a step further and get rid of all those static definitions which are completely unused except those of the current family we're loaded on.
IOW, you should make all family-specific assignments dynamic and get rid of
family_typesand those ops. Here's an example I did for K8:drivers/edac/amd64_edac.c +12
-2@@ -3656,8 +3656,18 @@ static struct amd64_family_type *per_family_init(struct amd64_pvt *pvt)switch (pvt->fam) {case 0xf : - fam_type = &family_types[K8_CPUS ]; - pvt->ops = &family_types[K8_CPUS ].ops; + fam_type->ctl_name ="K8" ; + fam_type->f1_id =PCI_DEVICE_ID_AMD_K8_NB_ADDRMAP ; + fam_type->f2_id =PCI_DEVICE_ID_AMD_K8_NB_MEMCTL ; + fam_type->max_mcs =2 ; + pvt->ops->early_channel_count = k8_early_channel_count; + pvt->ops->map_sysaddr_to_csrow = k8_map_sysaddr_to_csrow; + pvt->ops->dbam_to_cs = k8_dbam_to_chip_select; + pvt->ops->prep_chip_select = k8_prep_chip_selects; + pvt->ops->get_base_mask = read_dct_base_mask; + pvt->ops->get_misc_regs = __dump_misc_regs; + pvt->ops->get_mc_regs = read_mc_regs; + pvt->ops->populate_csrows = init_csrows;break ;case 0x10 :
Quoted 1 line
After that, pvt and
fam_typehave been properly set up.
Agreed, will create family_XXh_init() under per_family_init()'s switch.
At present, we are handling the family_type in 4/5 of this set. Will club them.
Quoted 5 lines
Quoted 5 lines
(quoted diff) +0
-0@@ -3735,7 +3784,16 @@ static int hw_info_get(struct amd64_pvt *pvt) if (ret) return ret;
Quoted 10 lines
Review static int hw_info_get(struct amd64_pvt *pvt) · line 3794
Quoted 9 lines
(quoted diff) +8
-1- read_mc_regs(pvt); + pvt->ops->get_mc_regs(pvt); + + pvt->ops->prep_chip_select(pvt); + + pvt->ops->get_base_mask(pvt); + + determine_memory_type(pvt); + edac_dbg(1, " DIMM type: %s\n", edac_mem_types[pvt->dram_type]);Move that dbg call at the end of
determine_memory_type().
Sure
Quoted 24 lines
Quoted 24 lines
(quoted diff) +3
-1+ + determine_ecc_sym_sz(pvt); return 0; }@@ -3786,7 +3844,7 @@ static int init_one_instance(struct amd64_pvt *pvt) setup_mci_misc_attrs(mci); - if (init_csrows(mci)) + if (pvt->ops->populate_csrows(mci)) mci->edac_cap = EDAC_FLAG_NONE; ret = -ENODEV;drivers/edac/amd64_edac.h +0
-1@@ -467,11 +467,17 @@ struct ecc_settings {* functions and per device encoding/decoding logic. */ struct low_ops { -int (*early_channel_count) (struct amd64_pvt *pvt);
Quoted 8 lines
drivers/edac/amd64_edac.h struct ecc_settings { · line 475
Quoted 7 lines
drivers/edac/amd64_edac.h +3
-1+int (*early_channel_count) (struct amd64_pvt *pvt);void (*map_sysaddr_to_csrow) (struct mem_ctl_info *mci,u64 sys_addr,struct err_info *); -int (*dbam_to_cs) (struct amd64_pvt *pvt,u8 dct, +int (*dbam_to_cs) (struct amd64_pvt *pvt,u8 dct,unsigned cs_mode,int cs_mask_nr); +void (*prep_chip_select) (struct amd64_pvt *pvt);That name should be "
prep_chip_selects" - plural.
Got it.
Quoted 38 lines
drivers/edac/amd64_edac.h struct ecc_settings { · line 480
Quoted 6 lines
drivers/edac/amd64_edac.h +5
-0+void (*get_base_mask) (struct amd64_pvt *pvt); +void (*get_misc_regs) (struct amd64_pvt *pvt); +void (*get_mc_regs) (struct amd64_pvt *pvt); +int (*populate_csrows) (struct mem_ctl_info *mci); +void (*get_umc_err_info) (struct mce *m,struct err_info *err);WARNING: Unnecessary space before function pointer arguments #652: FILE:
drivers/edac/amd64_edac.h:470:
+ int (*early_channel_count) (structamd64_pvt*pvt);WARNING: Unnecessary space before function pointer arguments #656: FILE:
drivers/edac/amd64_edac.h:473:
+ int (*dbam_to_cs) (structamd64_pvt*pvt, u8 dct,WARNING: Unnecessary space before function pointer arguments #658: FILE:
drivers/edac/amd64_edac.h:475:
+ void (*prep_chip_select) (structamd64_pvt*pvt);WARNING: Unnecessary space before function pointer arguments #659: FILE:
drivers/edac/amd64_edac.h:476:
+ void (*get_base_mask) (structamd64_pvt*pvt);WARNING: Unnecessary space before function pointer arguments #660: FILE:
drivers/edac/amd64_edac.h:477:
+ void (*get_misc_regs) (structamd64_pvt*pvt);WARNING: Unnecessary space before function pointer arguments #661: FILE:
drivers/edac/amd64_edac.h:478:
+ void (*get_mc_regs) (structamd64_pvt*pvt);WARNING: Unnecessary space before function pointer arguments #662: FILE:
drivers/edac/amd64_edac.h:479:
+ int (*populate_csrows) (structmem_ctl_info*mci);WARNING: Unnecessary space before function pointer arguments #663: FILE:
drivers/edac/amd64_edac.h:480:
+ void (*get_umc_err_info) (struct mce *m, structerr_info*err);
Quoted 5 lines
total: 0 errors, 8 warnings, 507 lines checked
Please integrate
scripts/checkpatch.plinto your patch creation workflow. Some of the warnings/errors *actually* make sense.
I have noticed these warnings. As there were previous definitions, i continued with similar indentation. Will address all of them.
Quoted 4 lines
--
Regards/Gruss,
Boris.
Thanks for the review.
Borislav Petkov
maintainerRe: [PATCH v6 3/5] EDAC/amd64: Extend family ops functions
Quoted 1 line · Naveen Krishna
Agreed, will create
family_XXh_init()under per_family_init()'s switch.
No, you need to simply assign the per-family stuff in that one big switch-case - no additional family_XXh_init() functions.
Signature · 4 lines
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquetteYazen Ghannam
maintainerRe: [PATCH v6 3/5] EDAC/amd64: Extend family ops functions
In reply to Chatradhi, Naveen KrishnaOn Thu, Nov 11, 2021 at 09:53:32PM +0530, Chatradhi, Naveen Krishna wrote:
...
Quoted 49 lines
Quoted 10 lines
Review
Quoted 9 lines
struct low_ops {(quoted diff) +3
-2- int (*early_channel_count) (struct amd64_pvt *pvt); + int (*early_channel_count) (struct amd64_pvt *pvt); void (*map_sysaddr_to_csrow) (struct mem_ctl_info *mci, u64 sys_addr, struct err_info *); - int (*dbam_to_cs) (struct amd64_pvt *pvt, u8 dct, + int (*dbam_to_cs) (struct amd64_pvt *pvt, u8 dct, unsigned cs_mode, int cs_mask_nr); + void (*prep_chip_select) (struct amd64_pvt *pvt);That name should be "
prep_chip_selects" - plural.Got it.
Quoted 38 lines
Review
Quoted 6 lines
(quoted diff) +5
-0+ void (*get_base_mask) (struct amd64_pvt *pvt); + void (*get_misc_regs) (struct amd64_pvt *pvt); + void (*get_mc_regs) (struct amd64_pvt *pvt); + int (*populate_csrows) (struct mem_ctl_info *mci); + void (*get_umc_err_info) (struct mce *m, struct err_info *err);WARNING: Unnecessary space before function pointer arguments #652: FILE:
drivers/edac/amd64_edac.h:470:
+ int (*early_channel_count) (structamd64_pvt*pvt);WARNING: Unnecessary space before function pointer arguments #656: FILE:
drivers/edac/amd64_edac.h:473:
+ int (*dbam_to_cs) (structamd64_pvt*pvt, u8 dct,WARNING: Unnecessary space before function pointer arguments #658: FILE:
drivers/edac/amd64_edac.h:475:
+ void (*prep_chip_select) (structamd64_pvt*pvt);WARNING: Unnecessary space before function pointer arguments #659: FILE:
drivers/edac/amd64_edac.h:476:
+ void (*get_base_mask) (structamd64_pvt*pvt);WARNING: Unnecessary space before function pointer arguments #660: FILE:
drivers/edac/amd64_edac.h:477:
+ void (*get_misc_regs) (structamd64_pvt*pvt);WARNING: Unnecessary space before function pointer arguments #661: FILE:
drivers/edac/amd64_edac.h:478:
+ void (*get_mc_regs) (structamd64_pvt*pvt);WARNING: Unnecessary space before function pointer arguments #662: FILE:
drivers/edac/amd64_edac.h:479:
+ int (*populate_csrows) (structmem_ctl_info*mci);WARNING: Unnecessary space before function pointer arguments #663: FILE:
drivers/edac/amd64_edac.h:480:
+ void (*get_umc_err_info) (struct mce *m, structerr_info*err);
Quoted 8 lines
Quoted 5 lines
total: 0 errors, 8 warnings, 507 lines checked
Please integrate
scripts/checkpatch.plinto your patch creation workflow. Some of the warnings/errors *actually* make sense.I have noticed these warnings. As there were previous definitions, i continued with similar indentation. Will address all of them.
Quoted 1 line
I've seen the same warning in some of my patches, but I've ignored it for readability. I'll need to make changes there too. :/
Thanks,
Yazen
Borislav Petkov
maintainerRe: [PATCH v6 3/5] EDAC/amd64: Extend family ops functions
Quoted 2 lines · Yazen Ghannam
I've seen the same warning in some of my patches, but I've ignored it for readability. I'll need to make changes there too. :/
If readability is of concern, you can fixup the issues you see in a pre-patch - I mean, you're touching the code so might as well fix them while at it.
What I really don't want to have is patches which simply fix random checkpatch issues and other whitespace crap because that becomes an insane mess with new people not really concentrating on fixing actual bugs but doing whitespace wankery only.
And having such patches always gets in the way when one does git archeology to figure out why something was done the way it is.
But it's fine to fix those if you're going to touch the code anyway.
HTH.
Signature · 4 lines
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquettePATCH v6 4/5 EDAC/amd64: Move struct fam_type into amd64_pvt structure
In reply to Naveen Krishna ChatradhiFrom: Muralidhara M K <[email protected]>
On heterogeneous systems, the GPU nodes are probed after the CPU nodes and will overwrites the family type set by CPU nodes.
Moving struct fam_type to struct amd64_pvt, instead of using fam_type as a global variable.
---
Changes since v5:
Added reviewed by Yazen
Changes since v4:
New patch, created based on a comment.
drivers/edac/amd64_edac.c | 58 +++++++++++++++++++-------------------- drivers/edac/amd64_edac.h | 2 ++ 2 files changed, 30 insertions(+), 30 deletions(-)
drivers/edac/amd64_edac.c +28 -30
@@ -13,8 +13,6 @@ module_param(ecc_enable_override, int, 0644);static struct msr __percpu *msrs; -static struct amd64_family_type *fam_type; -/* Per-node stuff */ static struct ecc_settings **ecc_stngs;
@@ -448,7 +446,7 @@ static void get_cs_base_and_mask(struct amd64_pvt *pvt, int csrow, u8 dct, for (i = 0; i < pvt->csels[dct].m_cnt; i++)#define for_each_umc (i) \ - for (i = 0; i < fam_type->max_mcs; i++) + for (i = 0; i < pvt->fam_type->max_mcs; i++)/* * @input_addr is an InputAddr associated with the node given by mci. Return the
@@ -3635,7 +3633,7 @@ static void setup_mci_misc_attrs(struct mem_ctl_info *mci) mci->edac_cap =determine_edac_cap (pvt); mci->mod_name =EDAC_MOD_STR ; - mci->ctl_name = fam_type->ctl_name; + mci->ctl_name = pvt->fam_type->ctl_name; mci->dev_name =pci_name (pvt->F3); mci->ctl_page_to_phys =NULL ;
@@ -3656,64 +3654,64 @@ static struct amd64_family_type *per_family_init(struct amd64_pvt *pvt)switch (pvt->fam) {case 0xf : - fam_type = &family_types[K8_CPUS ]; + pvt->fam_type = &family_types[K8_CPUS ]; pvt->ops = &family_types[K8_CPUS ].ops;break ;case 0x10 : - fam_type = &family_types[F10_CPUS ]; + pvt->fam_type = &family_types[F10_CPUS ]; pvt->ops = &family_types[F10_CPUS ].ops;break ;case 0x15 :if (pvt->model ==0x30 ) { - fam_type = &family_types[F15_M30H_CPUS ]; + pvt->fam_type = &family_types[F15_M30H_CPUS ]; pvt->ops = &family_types[F15_M30H_CPUS ].ops;break ; }else if (pvt->model ==0x60 ) { - fam_type = &family_types[F15_M60H_CPUS ]; + pvt->fam_type = &family_types[F15_M60H_CPUS ]; pvt->ops = &family_types[F15_M60H_CPUS ].ops;break ;/* Richland is only client */ }else if (pvt->model ==0x13 ) {return NULL ; }else { - fam_type = &family_types[F15_CPUS ]; + pvt->fam_type = &family_types[F15_CPUS ]; pvt->ops = &family_types[F15_CPUS ].ops; }break ;case 0x16 :if (pvt->model ==0x30 ) { - fam_type = &family_types[F16_M30H_CPUS ]; + pvt->fam_type = &family_types[F16_M30H_CPUS ]; pvt->ops = &family_types[F16_M30H_CPUS ].ops;break ; } - fam_type = &family_types[F16_CPUS ]; + pvt->fam_type = &family_types[F16_CPUS ]; pvt->ops = &family_types[F16_CPUS ].ops;break ;case 0x17 :if (pvt->model >=0x10 && pvt->model <=0x2f ) { - fam_type = &family_types[F17_M10H_CPUS ]; + pvt->fam_type = &family_types[F17_M10H_CPUS ]; pvt->ops = &family_types[F17_M10H_CPUS ].ops;break ; }else if (pvt->model >=0x30 && pvt->model <=0x3f ) { - fam_type = &family_types[F17_M30H_CPUS ]; + pvt->fam_type = &family_types[F17_M30H_CPUS ]; pvt->ops = &family_types[F17_M30H_CPUS ].ops;break ; }else if (pvt->model >=0x60 && pvt->model <=0x6f ) { - fam_type = &family_types[F17_M60H_CPUS ]; + pvt->fam_type = &family_types[F17_M60H_CPUS ]; pvt->ops = &family_types[F17_M60H_CPUS ].ops;break ; }else if (pvt->model >=0x70 && pvt->model <=0x7f ) { - fam_type = &family_types[F17_M70H_CPUS ]; + pvt->fam_type = &family_types[F17_M70H_CPUS ]; pvt->ops = &family_types[F17_M70H_CPUS ].ops;break ; } fallthrough;case 0x18 : - fam_type = &family_types[F17_CPUS ]; + pvt->fam_type = &family_types[F17_CPUS ]; pvt->ops = &family_types[F17_CPUS ].ops;if (pvt->fam ==0x18 )
@@ -3722,12 +3720,12 @@ static struct amd64_family_type *per_family_init(struct amd64_pvt *pvt)case 0x19 :if (pvt->model >=0x20 && pvt->model <=0x2f ) { - fam_type = &family_types[F17_M70H_CPUS ]; + pvt->fam_type = &family_types[F17_M70H_CPUS ]; pvt->ops = &family_types[F17_M70H_CPUS ].ops; - fam_type->ctl_name ="F19h_M20h" ; + pvt->fam_type->ctl_name ="F19h_M20h" ;break ; } - fam_type = &family_types[F19_CPUS ]; + pvt->fam_type = &family_types[F19_CPUS ]; pvt->ops = &family_types[F19_CPUS ].ops; family_types[F19_CPUS ].ctl_name ="F19h" ;break ;
@@ -3752,7 +3750,7 @@ static struct amd64_family_type *per_family_init(struct amd64_pvt *pvt)return NULL ; } -return fam_type; +return pvt->fam_type; }static const struct attribute_group *amd64_edac_attr_groups[] = {
@@ -3769,15 +3767,15 @@ static int hw_info_get(struct amd64_pvt *pvt)int ret;if (pvt->fam >=0x17 ) { - pvt->umc =kcalloc (fam_type->max_mcs,sizeof (struct amd64_umc ),GFP_KERNEL ); + pvt->umc =kcalloc (pvt->fam_type->max_mcs,sizeof (struct amd64_umc ),GFP_KERNEL );if (!pvt->umc)return -ENOMEM ; - pci_id1 = fam_type->f0_id; - pci_id2 = fam_type->f6_id; + pci_id1 = pvt->fam_type->f0_id; + pci_id2 = pvt->fam_type->f6_id; }else { - pci_id1 = fam_type->f1_id; - pci_id2 = fam_type->f2_id; + pci_id1 = pvt->fam_type->f1_id; + pci_id2 = pvt->fam_type->f2_id; } ret =reserve_mc_sibling_devs (pvt, pci_id1, pci_id2);
@@ -3832,7 +3830,7 @@ static int init_one_instance(struct amd64_pvt *pvt)* only one channel. Also, this simplifies handling later for the price * of a couple of KBs tops. */ - layers[1 ].size = fam_type->max_mcs; + layers[1 ].size = pvt->fam_type->max_mcs; layers[1 ].is_virt_csrow = false; mci =edac_mc_alloc (pvt->mc_node_id,ARRAY_SIZE (layers), layers,0 );
@@ -3862,7 +3860,7 @@ static bool instance_has_memory(struct amd64_pvt *pvt)bool cs_enabled = false;int cs =0 , dct =0 ; -for (dct =0 ; dct < fam_type->max_mcs; dct++) { +for (dct =0 ; dct < pvt->fam_type->max_mcs; dct++) {for_each_chip_select (cs, dct, pvt) cs_enabled |=csrow_enabled (cs, dct, pvt); }
@@ -3892,8 +3890,8 @@ static int probe_one_instance(unsigned int nid) pvt->F3 =F3 ; ret = -ENODEV ; - fam_type =per_family_init (pvt); -if (!fam_type) + pvt->fam_type =per_family_init (pvt); +if (!pvt->fam_type) goto err_enable; ret =hw_info_get (pvt);
@@ -3932,7 +3930,7 @@ static int probe_one_instance(unsigned int nid) goto err_enable; } - amd64_info("%s %sdetected (node %d).\n", fam_type->ctl_name, + amd64_info("%s %sdetected (node %d).\n", pvt->fam_type->ctl_name, (pvt->fam == 0xf ? (pvt->ext_model >= K8_REV_F ? "revF or later " : "revE or earlier ")
drivers/edac/amd64_edac.h +2 -0
@@ -389,6 +389,8 @@ struct amd64_pvt {enum mem_type dram_type;struct amd64_umc *umc;/* UMC registers */ + +struct amd64_family_type *fam_type; };enum err_codes {
Signature · 1 line
2.25.1
Borislav Petkov
maintainerRe: [PATCH v6 4/5] EDAC/amd64: Move struct fam_type into amd64_pvt structure
drivers/edac/amd64_edac.h struct amd64_pvt { · line 393
Quoted 10 lines · Naveen Krishna Chatradhi
drivers/edac/amd64_edac.h +2
-0@@ -389,6 +389,8 @@ struct amd64_pvt {enum mem_type dram_type;struct amd64_umc *umc;/* UMC registers */ + +struct amd64_family_type *fam_type;
With my suggestion to the previous patch to assign ops and per-family members dynamically, you can just as well get rid of struct amd64_family_type and put its members directly in the pvt structure.
Thx.
Signature · 4 lines
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquetteRe: [PATCH v6 4/5] EDAC/amd64: Move struct fam_type into amd64_pvt structure
Quoted 10 lines · Borislav Petkov
[CAUTION: External Email]
Quoted 7 lines · Naveen Krishna Chatradhi
drivers/edac/amd64_edac.h +0
-0@@ -389,6 +389,8 @@ struct amd64_pvt {enum mem_type dram_type;
Quoted 6 lines
drivers/edac/amd64_edac.h struct amd64_pvt { · line 393
Quoted 3 lines
drivers/edac/amd64_edac.h +2
-0struct amd64_umc *umc;/* UMC registers */ + +struct amd64_family_type *fam_type;With my suggestion to the previous patch to assign ops and per-family members dynamically, you can just as well get rid of struct
amd64_family_typeand put its members directly in the pvt structure.
Sure, will do. Thanks.
PATCH v6 5/5 EDAC/amd64: Enumerate memory on Aldebaran GPU nodes
In reply to Naveen Krishna ChatradhiOn newer heterogeneous systems with AMD CPUs, the data fabrics of the GPUs are connected directly via custom links.
One such system, where Aldebaran GPU nodes are connected to the Family 19h, model 30h family of CPU nodes, the Aldebaran GPUs can report memory errors via SMCA banks.
Aldebaran GPU support was added to DRM framework
https://lists.freedesktop.org/archives/amd-gfx/2021-February/059694.html
The GPU nodes comes with HBM2 memory in-built, ECC support is enabled by default and the UMCs on GPU node are different from the UMCs on CPU nodes.
GPU specific ops routines are defined to extend the amd64_edac module to enumerate HBM memory leveraging the existing edac and the amd64 specific data structures.
Note: The UMC Phys on GPU nodes are enumerated as csrows and the UMC channels connected to HBM banks are enumerated as ranks.
---
Changes since v5:
Removed else condition in per_family_init for 19h family
Changes since v4:
Split "f17_addr_mask_to_cs_size" instead as did in 3rd patch earlier
Changes since v3:
1. Bifurcated the GPU code from v2
Changes since v2:
1. Restored line deletions and handled minor comments
2. Modified commit message and some of the function comments
3. variable df_inst_id is introduced instead of umc_num
Changes since v1:
1. Modifed the commit message
2. Change the edac_cap
3. kept sizes of both cpu and noncpu together
4. return success if the !F3 condition true and remove unnecessary validation
drivers/edac/amd64_edac.c | 298 +++++++++++++++++++++++++++++++++----- drivers/edac/amd64_edac.h | 27 ++++ 2 files changed, 292 insertions(+), 33 deletions(-)
drivers/edac/amd64_edac.c +265 -33
@@ -1121,6 +1121,20 @@ static void debug_display_dimm_sizes_df(struct amd64_pvt *pvt, u8 ctrl) } } +static void debug_display_dimm_sizes_gpu (struct amd64_pvt *pvt,u8 ctrl) +{ +int size, cs =0 , cs_mode; + +edac_printk (KERN_DEBUG ,EDAC_MC ,"UMC%d chip selects:\n" , ctrl); + + cs_mode =CS_EVEN_PRIMARY |CS_ODD_PRIMARY ; + +for_each_chip_select (cs, ctrl, pvt) { + size = pvt->ops->dbam_to_cs (pvt, ctrl, cs_mode, cs); +amd64_info (EDAC_MC ": %d: %5dMB\n" , cs, size); + } +} +static void __dump_misc_regs_df (struct amd64_pvt *pvt) {struct amd64_umc *umc;
@@ -1165,6 +1179,27 @@ static void __dump_misc_regs_df(struct amd64_pvt *pvt) pvt->dhar, dhar_base(pvt)); } +static void __dump_misc_regs_gpu (struct amd64_pvt *pvt) +{ +struct amd64_umc *umc; +u32 i, umc_base; + +for_each_umc (i) { + umc_base =get_umc_base (i); + umc = &pvt->umc[i]; + +edac_dbg (1 ,"UMC%d UMC cfg: 0x%x\n" , i, umc->umc_cfg); +edac_dbg (1 ,"UMC%d SDP ctrl: 0x%x\n" , i, umc->sdp_ctrl); +edac_dbg (1 ,"UMC%d ECC ctrl: 0x%x\n" , i, umc->ecc_ctrl); +edac_dbg (1 ,"UMC%d All HBMs support ECC: yes\n" , i); + +debug_display_dimm_sizes_gpu (pvt, i); + } + +edac_dbg (1 ,"F0x104 (DRAM Hole Address): 0x%08x, base: 0x%08x\n" , + pvt->dhar,dhar_base (pvt)); +} +/* Display and decode various NB registers for debug purposes. */ static void __dump_misc_regs (struct amd64_pvt *pvt) {
@@ -1245,6 +1280,43 @@ static void f17_prep_chip_selects(struct amd64_pvt *pvt) } } +static void gpu_prep_chip_selects (struct amd64_pvt *pvt) +{ +int umc; + +for_each_umc (umc) { + pvt->csels[umc].b_cnt =8 ; + pvt->csels[umc].m_cnt =8 ; + } +} + +static void read_umc_base_mask_gpu (struct amd64_pvt *pvt) +{ +u32 base_reg, mask_reg; +u32 *base, *mask; +int umc, cs; + +for_each_umc (umc) { +for_each_chip_select (cs, umc, pvt) { + base_reg =get_umc_base_gpu (umc, cs) +UMCCH_BASE_ADDR ; + base = &pvt->csels[umc].csbases[cs]; + +if (!amd_smn_read (pvt->mc_node_id, base_reg, base)) { +edac_dbg (0 ," DCSB%d[%d]=0x%08x reg: 0x%x\n" , + umc, cs, *base, base_reg); + } + + mask_reg =get_umc_base_gpu (umc, cs) +UMCCH_ADDR_MASK ; + mask = &pvt->csels[umc].csmasks[cs]; + +if (!amd_smn_read (pvt->mc_node_id, mask_reg, mask)) { +edac_dbg (0 ," DCSM%d[%d]=0x%08x reg: 0x%x\n" , + umc, cs, *mask, mask_reg); + } + } + } +} +static void read_umc_base_mask (struct amd64_pvt *pvt) {u32 umc_base_reg, umc_base_reg_sec;
@@ -1743,6 +1815,19 @@ static int f17_early_channel_count(struct amd64_pvt *pvt)return channels; } +static int gpu_early_channel_count (struct amd64_pvt *pvt) +{ +int i, channels =0 ; + +/* The memory channels in case of GPUs are fully populated */ +for_each_umc (i) + channels += pvt->csels[i].b_cnt; + +amd64_info ("MCT channel count: %d\n" , channels); + +return channels; +} +static int ddr3_cs_size (unsigned i,bool dct_width) {unsigned shift =0 ;
@@ -1870,11 +1955,46 @@ static int f16_dbam_to_chip_select(struct amd64_pvt *pvt, u8 dct,return ddr3_cs_size (cs_mode, false); } +static int __addr_mask_to_cs_size (u32 addr_mask_orig,unsigned int cs_mode, +int csrow_nr,int dimm) +{ +u32 msb, weight, num_zero_bits; +u32 addr_mask_deinterleaved; +int size =0 ; + +/* +* The number of zero bits in the mask is equal to the number of bits +* in a full mask minus the number of bits in the current mask. +* +* The MSB is the number of bits in the full mask because BIT[0] is +* always 0. +* +* In the special 3 Rank interleaving case, a single bit is flipped +* without swapping with the most significant bit. This can be handled +* by keeping the MSB where it is and ignoring the single zero bit. +*/ + msb =fls (addr_mask_orig) -1 ; + weight =hweight_long (addr_mask_orig); + num_zero_bits = msb - weight - !!(cs_mode &CS_3R_INTERLEAVE ); + +/* Take the number of zero bits off from the top of the mask. */ + addr_mask_deinterleaved =GENMASK_ULL (msb - num_zero_bits,1 ); + +edac_dbg (1 ,"CS%d DIMM%d AddrMasks:\n" , csrow_nr, dimm); +edac_dbg (1 ," Original AddrMask: 0x%x\n" , addr_mask_orig); +edac_dbg (1 ," Deinterleaved AddrMask: 0x%x\n" , addr_mask_deinterleaved); + +/* Register [31:1] = Address [39:9]. Size is in kBs here. */ + size = (addr_mask_deinterleaved >>2 ) +1 ; + +/* Return size in MBs. */ +return size >>10 ; +} +static int f17_addr_mask_to_cs_size (struct amd64_pvt *pvt,u8 umc,unsigned int cs_mode,int csrow_nr) { -u32 addr_mask_orig, addr_mask_deinterleaved; -u32 msb, weight, num_zero_bits; +u32 addr_mask_orig;int dimm, size =0 ;/* No Chip Selects are enabled. */
@@ -1902,33 +2022,15 @@ static int f17_addr_mask_to_cs_size(struct amd64_pvt *pvt, u8 umc,else addr_mask_orig = pvt->csels[umc].csmasks[dimm]; -/* -* The number of zero bits in the mask is equal to the number of bits -* in a full mask minus the number of bits in the current mask. -* -* The MSB is the number of bits in the full mask because BIT[0] is -* always 0. -* -* In the special 3 Rank interleaving case, a single bit is flipped -* without swapping with the most significant bit. This can be handled -* by keeping the MSB where it is and ignoring the single zero bit. -*/ - msb =fls (addr_mask_orig) -1 ; - weight =hweight_long (addr_mask_orig); - num_zero_bits = msb - weight - !!(cs_mode &CS_3R_INTERLEAVE ); - -/* Take the number of zero bits off from the top of the mask. */ - addr_mask_deinterleaved =GENMASK_ULL (msb - num_zero_bits,1 ); - -edac_dbg (1 ,"CS%d DIMM%d AddrMasks:\n" , csrow_nr, dimm); -edac_dbg (1 ," Original AddrMask: 0x%x\n" , addr_mask_orig); -edac_dbg (1 ," Deinterleaved AddrMask: 0x%x\n" , addr_mask_deinterleaved); +return __addr_mask_to_cs_size (addr_mask_orig, cs_mode, csrow_nr, dimm); +} -/* Register [31:1] = Address [39:9]. Size is in kBs here. */ - size = (addr_mask_deinterleaved >>2 ) +1 ; +static int gpu_addr_mask_to_cs_size (struct amd64_pvt *pvt,u8 umc, +unsigned int cs_mode,int csrow_nr) +{ +u32 addr_mask_orig = pvt->csels[umc].csmasks[csrow_nr]; -/* Return size in MBs. */ -return size >>10 ; +return __addr_mask_to_cs_size (addr_mask_orig, cs_mode, csrow_nr, csrow_nr >>1 ); }static void read_dram_ctl_register (struct amd64_pvt *pvt)
@@ -2516,9 +2618,12 @@ static void debug_display_dimm_sizes(struct amd64_pvt *pvt, u8 ctrl)/* Prototypes for family specific ops routines */ static int init_csrows (struct mem_ctl_info *mci);static int init_csrows_df (struct mem_ctl_info *mci); +static int init_csrows_gpu (struct mem_ctl_info *mci);static void read_mc_regs (struct amd64_pvt *pvt);static void __read_mc_regs_df (struct amd64_pvt *pvt); +static void __read_mc_regs_gpu (struct amd64_pvt *pvt);static void update_umc_err_info (struct mce *m,struct err_info *err); +static void update_umc_err_info_gpu (struct mce *m,struct err_info *err);static const struct low_ops k8_ops = { .early_channel_count = k8_early_channel_count,
@@ -2597,6 +2702,17 @@ static const struct low_ops f17_ops = { .get_umc_err_info = update_umc_err_info, }; +static const struct low_ops gpu_ops = { + .early_channel_count = gpu_early_channel_count, + .dbam_to_cs = gpu_addr_mask_to_cs_size, + .prep_chip_select = gpu_prep_chip_selects, + .get_base_mask = read_umc_base_mask_gpu, + .get_misc_regs = __dump_misc_regs_gpu, + .get_mc_regs = __read_mc_regs_gpu, + .populate_csrows = init_csrows_gpu, + .get_umc_err_info = update_umc_err_info_gpu, +}; +static struct amd64_family_type family_types[] = { [K8_CPUS ] = { .ctl_name ="K8" ,
@@ -2689,6 +2805,14 @@ static struct amd64_family_type family_types[] = { .max_mcs = 8, .ops = f17_ops, }, + [ALDEBARAN_GPUS] = { + .ctl_name = "ALDEBARAN", + .f0_id = PCI_DEVICE_ID_AMD_ALDEBARAN_DF_F0, + .f6_id = PCI_DEVICE_ID_AMD_ALDEBARAN_DF_F6, + .max_mcs = 4, + .ops = gpu_ops, + }, + };/*
@@ -2947,12 +3071,38 @@ static void update_umc_err_info(struct mce *m, struct err_info *err) err->csrow = m->synd &0x7 ; } +/* +* The CPUs have one channel per UMC, So UMC number is equivalent to a +* channel number. The GPUs have 8 channels per UMC, so the UMC number no +* longer works as a channel number. +* The channel number within a GPU UMC is given in MCA_IPID[15:12]. +* However, the IDs are split such that two UMC values go to one UMC, and +* the channel numbers are split in two groups of four. +* +* Refer comment on get_umc_base_gpu() from amd64_edac.h +* +* For example, +* UMC0 CH[3:0] = 0x0005[3:0]000 +* UMC0 CH[7:4] = 0x0015[3:0]000 +* UMC1 CH[3:0] = 0x0025[3:0]000 +* UMC1 CH[7:4] = 0x0035[3:0]000 +*/ +static void update_umc_err_info_gpu (struct mce *m,struct err_info *err) +{ +u8 ch = (m->ipid &GENMASK (31 ,0 )) >>20 ; +u8 phy = ((m->ipid >>12 ) &0xf ); + + err->channel = ch %2 ? phy +4 : phy; + err->csrow = phy; +} +static void decode_umc_error (int node_id,struct mce *m) {u8 ecc_type = (m->status >>45 ) &0x3 ;struct mem_ctl_info *mci;struct amd64_pvt *pvt;struct err_info err; +u8 df_inst_id;u64 sys_addr; mci =edac_mc_find (node_id);
@@ -2982,7 +3132,17 @@ static void decode_umc_error(int node_id, struct mce *m) pvt->ops->get_umc_err_info (m, &err); -if (umc_normaddr_to_sysaddr (m->addr, pvt->mc_node_id, err.channel, &sys_addr)) { +/* +* GPU node has #phys[X] which has #channels[Y] each. +* On GPUs, df_inst_id = [X] * num_ch_per_phy + [Y]. +* On CPUs, "Channel"="UMC Number"="DF Instance ID". +*/ +if (pvt->is_gpu) + df_inst_id = (err.csrow * pvt->channel_count / mci->nr_csrows) + err.channel; +else + df_inst_id = err.channel; + +if (umc_normaddr_to_sysaddr (m->addr, pvt->mc_node_id, df_inst_id, &sys_addr)) { err.err_code =ERR_NORM_ADDR ; goto log_error; }
@@ -3146,6 +3306,25 @@ static void __read_mc_regs_df(struct amd64_pvt *pvt)amd64_read_pci_cfg (pvt->F0,DF_DHAR , &pvt->dhar); } +static void __read_mc_regs_gpu (struct amd64_pvt *pvt) +{ +u8 nid = pvt->mc_node_id; +struct amd64_umc *umc; +u32 i, umc_base; + +/* Read registers from each UMC */ +for_each_umc (i) { + umc_base =get_umc_base_gpu (i,0 ); + umc = &pvt->umc[i]; + +amd_smn_read (nid, umc_base +UMCCH_UMC_CFG , &umc->umc_cfg); +amd_smn_read (nid, umc_base +UMCCH_SDP_CTRL , &umc->sdp_ctrl); +amd_smn_read (nid, umc_base +UMCCH_ECC_CTRL , &umc->ecc_ctrl); + } + +amd64_read_pci_cfg (pvt->F0,DF_DHAR , &pvt->dhar); +} +/* * Retrieve the hardware registers of the memory controller (this includes the * 'Address Map' and 'Misc' device regs)
@@ -3241,7 +3420,10 @@ static u32 get_csrow_nr_pages(struct amd64_pvt *pvt, u8 dct, int csrow_nr_orig) csrow_nr >>=1 ; cs_mode =DBAM_DIMM (csrow_nr, dbam); }else { - cs_mode =f17_get_cs_mode (csrow_nr >>1 , dct, pvt); +if (pvt->is_gpu) + cs_mode =CS_EVEN_PRIMARY |CS_ODD_PRIMARY ; +else + cs_mode =f17_get_cs_mode (csrow_nr >>1 , dct, pvt); } nr_pages = pvt->ops->dbam_to_cs (pvt, dct, cs_mode, csrow_nr);
@@ -3298,6 +3480,35 @@ static int init_csrows_df(struct mem_ctl_info *mci)return empty; } +static int init_csrows_gpu (struct mem_ctl_info *mci) +{ +struct amd64_pvt *pvt = mci->pvt_info; +struct dimm_info *dimm; +int empty =1 ; +u8 umc, cs; + +for_each_umc (umc) { +for_each_chip_select (cs, umc, pvt) { +if (!csrow_enabled (cs, umc, pvt)) +continue ; + + empty =0 ; + dimm = mci->csrows[umc]->channels[cs]->dimm; + +edac_dbg (1 ,"MC node: %d, csrow: %d\n" , + pvt->mc_node_id, cs); + + dimm->nr_pages =get_csrow_nr_pages (pvt, umc, cs); + dimm->mtype =MEM_HBM2 ; + dimm->edac_mode =EDAC_SECDED ; + dimm->dtype =DEV_X16 ; + dimm->grain =64 ; + } + } + +return empty; +} +/* * Initialize the array of csrow attribute instances, based on the values * from pci config hardware registers.
@@ -3539,6 +3750,10 @@ static bool ecc_enabled(struct amd64_pvt *pvt)u8 ecc_en =0 , i;u32 value; +/* ECC is enabled by default on GPU nodes */ +if (pvt->is_gpu) +return true; +if (boot_cpu_data.x86 >=0x17 ) {u8 umc_en_mask =0 , ecc_en_mask =0 ;struct amd64_umc *umc;
@@ -3622,7 +3837,10 @@ static void setup_mci_misc_attrs(struct mem_ctl_info *mci) mci->edac_ctl_cap =EDAC_FLAG_NONE ;if (pvt->umc) { -f17h_determine_edac_ctl_cap (mci, pvt); +if (pvt->is_gpu) + mci->edac_ctl_cap |=EDAC_FLAG_SECDED ; +else +f17h_determine_edac_ctl_cap (mci, pvt); }else {if (pvt->nbcap &NBCAP_SECDED ) mci->edac_ctl_cap |=EDAC_FLAG_SECDED ;
@@ -3724,6 +3942,17 @@ static struct amd64_family_type *per_family_init(struct amd64_pvt *pvt) pvt->ops = &family_types[F17_M70H_CPUS ].ops; pvt->fam_type->ctl_name ="F19h_M20h" ;break ; + }else if (pvt->model >=0x30 && pvt->model <=0x3f ) { +if (pvt->mc_node_id >=amd_cpu_node_count ()) { + pvt->fam_type = &family_types[ALDEBARAN_GPUS ]; + pvt->ops = &family_types[ALDEBARAN_GPUS ].ops; + pvt->is_gpu = true; + }else { + pvt->fam_type = &family_types[F19_CPUS ]; + pvt->ops = &family_types[F19_CPUS ].ops; + family_types[F19_CPUS ].ctl_name ="F19h_M30h" ; + } +break ; } pvt->fam_type = &family_types[F19_CPUS ]; pvt->ops = &family_types[F19_CPUS ].ops;
@@ -3791,7 +4020,9 @@ static int hw_info_get(struct amd64_pvt *pvt)determine_memory_type (pvt);edac_dbg (1 ," DIMM type: %s\n" , edac_mem_types[pvt->dram_type]); -determine_ecc_sym_sz (pvt); +/* ECC symbol size is not available on GPU nodes */ +if (!pvt->is_gpu) +determine_ecc_sym_sz (pvt);return 0 ; }
@@ -3819,9 +4050,10 @@ static int init_one_instance(struct amd64_pvt *pvt)if (pvt->channel_count <0 )return ret; +/* Define layers for CPU and GPU nodes */ ret = -ENOMEM ; layers[0 ].type =EDAC_MC_LAYER_CHIP_SELECT ; - layers[0 ].size = pvt->csels[0 ].b_cnt; + layers[0 ].size = pvt->is_gpu ? pvt->fam_type->max_mcs : pvt->csels[0 ].b_cnt; layers[0 ].is_virt_csrow = true; layers[1 ].type =EDAC_MC_LAYER_CHANNEL ;
@@ -3830,7 +4062,7 @@ static int init_one_instance(struct amd64_pvt *pvt)* only one channel. Also, this simplifies handling later for the price * of a couple of KBs tops. */ - layers[1 ].size = pvt->fam_type->max_mcs; + layers[1 ].size = pvt->is_gpu ? pvt->csels[0 ].b_cnt : pvt->fam_type->max_mcs; layers[1 ].is_virt_csrow = false; mci =edac_mc_alloc (pvt->mc_node_id,ARRAY_SIZE (layers), layers,0 );
drivers/edac/amd64_edac.h +27 -0
@@ -126,6 +126,8 @@#define PCI_DEVICE_ID_AMD_17H_M70H_DF_F6 0x1446#define PCI_DEVICE_ID_AMD_19H_DF_F0 0x1650#define PCI_DEVICE_ID_AMD_19H_DF_F6 0x1656 +#define PCI_DEVICE_ID_AMD_ALDEBARAN_DF_F0 0x14d0 +#define PCI_DEVICE_ID_AMD_ALDEBARAN_DF_F6 0x14d6/* * Function 1 - Address Map
@@ -298,6 +300,7 @@ enum amd_families {F17_M60H_CPUS ,F17_M70H_CPUS ,F19_CPUS , +ALDEBARAN_GPUS , NUM_FAMILIES, };
@@ -391,6 +394,8 @@ struct amd64_pvt {struct amd64_umc *umc;/* UMC registers */ struct amd64_family_type *fam_type; + +bool is_gpu; };enum err_codes {
@@ -412,6 +417,28 @@ struct err_info {u32 offset; }; +static inline u32 get_umc_base_gpu (u8 umc,u8 channel) +{ +/* +* On CPUs, there is one channel per UMC, so UMC numbering equals +* channel numbering. On GPUs, there are eight channels per UMC, +* so the channel numbering is different from UMC numbering. +* +* On CPU nodes channels are selected in 6th nibble +* UMC chY[3:0]= [(chY*2 + 1) : (chY*2)]50000; +* +* On GPU nodes channels are selected in 3rd nibble +* HBM chX[3:0]= [Y ]5X[3:0]000; +* HBM chX[7:4]= [Y+1]5X[3:0]000 +*/ + umc *=2 ; + +if (channel >=4 ) + umc++; + +return 0x50000 + (umc <<20 ) + ((channel %4 ) <<12 ); +} +static inline u32 get_umc_base (u8 channel) {/* chY: 0xY50000 */
Signature · 1 line
2.25.1
Borislav Petkov
maintainerRe: [PATCH v6 5/5] EDAC/amd64: Enumerate memory on Aldebaran GPU nodes
Quoted 13 lines · Naveen Krishna Chatradhi
On newer heterogeneous systems with AMD CPUs, the data fabrics of the GPUs are connected directly via custom links.
One such system, where Aldebaran GPU nodes are connected to the Family 19h, model 30h family of CPU nodes, the Aldebaran GPUs can report memory errors via SMCA banks.
Aldebaran GPU support was added to DRM framework
https://lists.freedesktop.org/archives/amd-gfx/2021-February/059694.htmlThe GPU nodes comes with HBM2 memory in-built, ECC support is enabled by default and the UMCs on GPU node are different from the UMCs on CPU nodes.
Quoted 6 lines
GPU specific ops routines are defined to extend the
amd64_edacmodule to enumerate HBM memory leveraging the existing edac and the amd64 specific data structures.Note: The UMC Phys on GPU nodes are enumerated as csrows and the UMC channels connected to HBM banks are enumerated as ranks.
For all your future commit messages, fromDocumentation/process/submitting-patches.rst:
"Describe your changes in imperative mood, e.g. "make xyzzy do frotz"
instead of "[This patch] makes xyzzy do frotz" or "[I] changed xyzzy to do frotz", as if you are giving orders to the codebase to change its behaviour."
Also, do not talk about what your patch does - that should hopefully be visible in the diff itself. Rather, talk about *why* you're doing what you're doing.
Quoted 57 lines
Cc Yazen Ghannam <[email protected]>Co-developed-by Muralidhara M K <[email protected]>Signed-off-by Muralidhara M K <[email protected]>Signed-off-by Naveen Krishna Chatradhi <[email protected]>---
Changes since v5:
Removed else condition inper_family_initfor 19h familyChanges since v4:
Split "f17_addr_mask_to_cs_size" instead as did in 3rd patch earlierChanges since v3:
1. Bifurcated the GPU code from v2Changes since v2:
1. Restored line deletions and handled minor comments
2. Modified commit message and some of the function comments
3. variabledf_inst_idis introduced instead ofumc_numChanges since v1:
1. Modifed the commit message
2. Change theedac_cap
3. kept sizes of both cpu and noncpu together
4. return success if the !F3 condition true and remove unnecessary validationdrivers/edac/amd64_edac.c | 298 +++++++++++++++++++++++++++++++++----- drivers/edac/amd64_edac.h | 27 ++++ 2 files changed, 292 insertions(+), 33 deletions(-)drivers/edac/amd64_edac.c +14
-0@@ -1121,6 +1121,20 @@ static void debug_display_dimm_sizes_df(struct amd64_pvt *pvt, u8 ctrl) } } +static void debug_display_dimm_sizes_gpu (struct amd64_pvt *pvt,u8 ctrl) +{ +int size, cs =0 , cs_mode; + +edac_printk (KERN_DEBUG ,EDAC_MC ,"UMC%d chip selects:\n" , ctrl); + + cs_mode =CS_EVEN_PRIMARY |CS_ODD_PRIMARY ; + +for_each_chip_select (cs, ctrl, pvt) { + size = pvt->ops->dbam_to_cs (pvt, ctrl, cs_mode, cs); +amd64_info (EDAC_MC ": %d: %5dMB\n" , cs, size); + } +} +static void __dump_misc_regs_df (struct amd64_pvt *pvt) {struct amd64_umc *umc;
drivers/edac/amd64_edac.c static void __dump_misc_regs_df(struct amd64_pvt *pvt) · line 1182
Quoted 4 lines
drivers/edac/amd64_edac.c +1
-0@@ -1165,6 +1179,27 @@ static void __dump_misc_regs_df(struct amd64_pvt *pvt) pvt->dhar, dhar_base(pvt)); } +static void __dump_misc_regs_gpu (struct amd64_pvt *pvt)
The function pointer this gets assigned to is called *get*_misc_regs. But this function is is doing *dump*.
When I see __dump_misc_regs_gpu() I'd expect this function to be called by a higher level dump_misc_regs() as the "__" denotes layering usually.
There is, in fact, dump_misc_regs() but that one calls ->get_misc_regs().
So this all needs fixing - right now I see a mess.
Also, there's <function_name>_gpu and gpu_<function_name> with the "gpu" being either prefix or suffix. You need to fix the current ones to be only prefixes - in a pre-patch - and then add yours as prefixes only too.
And in talking about pre-patches - this one is doing a bunch of things at once and needs splitting. You do the preparatory work like carving out common functionality and other refactoring in pre-patches, and then you add the new functionality ontop.
Also, I don't like ->is_gpu one bit, it being sprinkled like that around the code. This says that the per-family attrs and ops assignment is lacking.
drivers/edac/amd64_edac.c static void decode_umc_error(int node_id, struct mce *m) · line 3139
Quoted 10 lines
drivers/edac/amd64_edac.c +5
-1@@ -2982,7 +3132,17 @@ static void decode_umc_error(int node_id, struct mce *m) pvt->ops->get_umc_err_info (m, &err); -if (umc_normaddr_to_sysaddr (m->addr, pvt->mc_node_id, err.channel, &sys_addr)) { +/* +* GPU node has #phys[X] which has #channels[Y] each. +* On GPUs, df_inst_id = [X] * num_ch_per_phy + [Y]. +* On CPUs, "Channel"="UMC Number"="DF Instance ID". +*/
This comment doesn't look like it is destined for human beings to read but maybe to be parsed by programs?
drivers/edac/amd64_edac.c static void decode_umc_error(int node_id, struct mce *m) · line 3141
Quoted 2 lines
drivers/edac/amd64_edac.c +2
-0+if (pvt->is_gpu) + df_inst_id = (err.csrow * pvt->channel_count / mci->nr_csrows) + err.channel;
I'm not sure we want to log ECCs from the GPUs: what is going to happen to them, how does the further error recovery look like?
Also, EDAC sysfs structure currently has only DIMMs, below's from my box.
I don't see how that structure fits the GPUs so here's the $10^6
question: why does EDAC need to know about GPUs?
What is the strategy here?
Your 0th message talks about the "what" but what gets added is not important - the "why" is.
$ grep -r . /sys/devices/system/edac/mc/ 2>/dev/null /sys/devices/system/edac/mc/power/runtime_active_time:0 /sys/devices/system/edac/mc/power/runtime_status:unsupported /sys/devices/system/edac/mc/power/runtime_suspended_time:0 /sys/devices/system/edac/mc/power/control:auto /sys/devices/system/edac/mc/mc0/ce_count:0 /sys/devices/system/edac/mc/mc0/rank7/dimm_ue_count:0 /sys/devices/system/edac/mc/mc0/rank7/dimm_mem_type:Unbuffered-DDR4 /sys/devices/system/edac/mc/mc0/rank7/power/runtime_active_time:0 /sys/devices/system/edac/mc/mc0/rank7/power/runtime_status:unsupported /sys/devices/system/edac/mc/mc0/rank7/power/runtime_suspended_time:0 /sys/devices/system/edac/mc/mc0/rank7/power/control:auto /sys/devices/system/edac/mc/mc0/rank7/dimm_dev_type:Unknown /sys/devices/system/edac/mc/mc0/rank7/size:8192 /sys/devices/system/edac/mc/mc0/rank7/dimm_ce_count:0 /sys/devices/system/edac/mc/mc0/rank7/dimm_label:mc#0csrow#3channel#1 /sys/devices/system/edac/mc/mc0/rank7/dimm_location:csrow 3 channel 1 /sys/devices/system/edac/mc/mc0/rank7/dimm_edac_mode:SECDED /sys/devices/system/edac/mc/mc0/topmem:0x00000000e0000000 /sys/devices/system/edac/mc/mc0/mc_name:F17h /sys/devices/system/edac/mc/mc0/rank5/dimm_ue_count:0 /sys/devices/system/edac/mc/mc0/rank5/dimm_mem_type:Unbuffered-DDR4 /sys/devices/system/edac/mc/mc0/rank5/power/runtime_active_time:0 /sys/devices/system/edac/mc/mc0/rank5/power/runtime_status:unsupported /sys/devices/system/edac/mc/mc0/rank5/power/runtime_suspended_time:0 /sys/devices/system/edac/mc/mc0/rank5/power/control:auto /sys/devices/system/edac/mc/mc0/rank5/dimm_dev_type:Unknown /sys/devices/system/edac/mc/mc0/rank5/size:8192 /sys/devices/system/edac/mc/mc0/rank5/dimm_ce_count:0 /sys/devices/system/edac/mc/mc0/rank5/dimm_label:mc#0csrow#2channel#1 /sys/devices/system/edac/mc/mc0/rank5/dimm_location:csrow 2 channel 1 /sys/devices/system/edac/mc/mc0/rank5/dimm_edac_mode:SECDED /sys/devices/system/edac/mc/mc0/dram_hole:0 0 0 /sys/devices/system/edac/mc/mc0/ce_noinfo_count:0 ...
Signature · 4 lines
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquetteRe: [PATCH v6 5/5] EDAC/amd64: Enumerate memory on Aldebaran GPU nodes
Hi Boris
Quoted 25 lines · Borislav Petkov
[CAUTION: External Email]
Quoted 13 lines · Naveen Krishna Chatradhi
On newer heterogeneous systems with AMD CPUs, the data fabrics of the GPUs are connected directly via custom links.
One such system, where Aldebaran GPU nodes are connected to the Family 19h, model 30h family of CPU nodes, the Aldebaran GPUs can report memory errors via SMCA banks.
The GPU nodes comes with HBM2 memory in-built, ECC support is enabled by default and the UMCs on GPU node are different from the UMCs on CPU nodes.
Quoted 6 lines
GPU specific ops routines are defined to extend the
amd64_edacmodule to enumerate HBM memory leveraging the existing edac and the amd64 specific data structures.Note: The UMC Phys on GPU nodes are enumerated as csrows and the UMC channels connected to HBM banks are enumerated as ranks.
For all your future commit messages, from
Documentation/process/submitting-patches.rst:
Quoted 8 lines
"Describe your changes in imperative mood, e.g. "make xyzzy do frotz"
instead of "[This patch] makes xyzzy do frotz" or "[I] changed xyzzy to do frotz", as if you are giving orders to the codebase to change its behaviour."Also, do not talk about what your patch does - that should hopefully be visible in the diff itself. Rather, talk about *why* you're doing what you're doing.
Sure.
Quoted 67 lines
Quoted 57 lines
Cc Yazen Ghannam <[email protected]>Co-developed-by Muralidhara M K <[email protected]>Signed-off-by Muralidhara M K <[email protected]>Signed-off-by Naveen Krishna Chatradhi <[email protected]>---
Changes since v5:
Removed else condition inper_family_initfor 19h familyChanges since v4:
Split "f17_addr_mask_to_cs_size" instead as did in 3rd patch earlierChanges since v3:
1. Bifurcated the GPU code from v2Changes since v2:
1. Restored line deletions and handled minor comments
2. Modified commit message and some of the function comments
3. variabledf_inst_idis introduced instead ofumc_numChanges since v1:
1. Modifed the commit message
2. Change theedac_cap
3. kept sizes of both cpu and noncpu together
4. return success if the !F3 condition true and remove unnecessary validationdrivers/edac/amd64_edac.c | 298 +++++++++++++++++++++++++++++++++----- drivers/edac/amd64_edac.h | 27 ++++ 2 files changed, 292 insertions(+), 33 deletions(-)drivers/edac/amd64_edac.c +14
-0@@ -1121,6 +1121,20 @@ static void debug_display_dimm_sizes_df(struct amd64_pvt *pvt, u8 ctrl) } } +static void debug_display_dimm_sizes_gpu (struct amd64_pvt *pvt,u8 ctrl) +{ +int size, cs =0 , cs_mode; + +edac_printk (KERN_DEBUG ,EDAC_MC ,"UMC%d chip selects:\n" , ctrl); + + cs_mode =CS_EVEN_PRIMARY |CS_ODD_PRIMARY ; + +for_each_chip_select (cs, ctrl, pvt) { + size = pvt->ops->dbam_to_cs (pvt, ctrl, cs_mode, cs); +amd64_info (EDAC_MC ": %d: %5dMB\n" , cs, size); + } +} +static void __dump_misc_regs_df (struct amd64_pvt *pvt) {struct amd64_umc *umc;drivers/edac/amd64_edac.c static void __dump_misc_regs_df(struct amd64_pvt *pvt) · line 1182
Quoted 4 lines
drivers/edac/amd64_edac.c +1
-0@@ -1165,6 +1179,27 @@ static void __dump_misc_regs_df(struct amd64_pvt *pvt) pvt->dhar, dhar_base(pvt)); } +static void __dump_misc_regs_gpu (struct amd64_pvt *pvt)The function pointer this gets assigned to is called *get*_misc_regs. But this function is is doing *dump*.
When I see
__dump_misc_regs_gpu()I'd expect this function to be called by a higher leveldump_misc_regs()as the "__" denotes layering usually.
Quoted 8 lines
There is, in fact,
dump_misc_regs()but that one calls ->get_misc_regs().So this all needs fixing - right now I see a mess.
Also, there's <function_name>_gpu and gpu_<function_name> with the "gpu" being either prefix or suffix. You need to fix the current ones to be only prefixes - in a pre-patch - and then add yours as prefixes only too.
Will modify the names to use prefixes
Quoted 5 lines
And in talking about pre-patches - this one is doing a bunch of things at once and needs splitting. You do the preparatory work like carving out common functionality and other refactoring in pre-patches, and then you add the new functionality ontop.
Sure, i will split this.
Quoted 4 lines
Also, I don't like ->is_gpu one bit, it being sprinkled like that around the code. This says that the per-family attrs and ops assignment is lacking.
Yes, adding few more ops routines should help get rid of this if conditions.
Quoted 6 lines
Quoted 6 lines
drivers/edac/amd64_edac.c +0
-0@@ -2982,7 +3132,17 @@ static void decode_umc_error(int node_id, struct mce *m) pvt->ops->get_umc_err_info (m, &err);
Quoted 8 lines
drivers/edac/amd64_edac.c static void decode_umc_error(int node_id, struct mce *m) · line 3139
Quoted 6 lines
drivers/edac/amd64_edac.c +5
-1-if (umc_normaddr_to_sysaddr (m->addr, pvt->mc_node_id, err.channel, &sys_addr)) { +/* +* GPU node has #phys[X] which has #channels[Y] each. +* On GPUs, df_inst_id = [X] * num_ch_per_phy + [Y]. +* On CPUs, "Channel"="UMC Number"="DF Instance ID". +*/ This comment doesn't look like it is destined for human beings to read but maybe to be parsed by programs?
The present system supports the following setup
A GPU node includes four Unified Memory Controllers (UMC). Each UMC contains eight UMCCH instances.
Each UMCCH controls one 128-bit HBM2e (2GB) channel. The UMC interfaces to the system via the Data Fabric (DF) Coherent Slave.
For a generalized function, i will modify the comment as
"A GPU node has 'X' number of UMC PHYs and 'Y' number of UMCCH instances each. This results in 'X*Y' number of
instances in the Data Fabric. Therefore the Data Fabric ID of an instance can be found with the following formula:
df_inst_id = 'X' * number of channels per PHY + 'Y'
Quoted 5 lines
drivers/edac/amd64_edac.c static void decode_umc_error(int node_id, struct mce *m) · line 3141
Quoted 3 lines
drivers/edac/amd64_edac.c +2
-0+if (pvt->is_gpu) + df_inst_id = (err.csrow * pvt->channel_count / mci->nr_csrows) + err.channel;I'm not sure we want to log ECCs from the GPUs: what is going to happen to them, how does the further error recovery look like?
AMD GPU has support for memory error reporting via the SMCA register banks, functionality is similar to the CPU dies.
The customer/end users of this product want to count memory errors and they want to do this in the OS using similar
mechanisms as they are used to on the CPU side.
Quoted 6 lines
Also, EDAC sysfs structure currently has only DIMMs, below's from my box.
I don't see how that structure fits the GPUs so here's the $10^6
question: why does EDAC need to know about GPUs?
The errors are not specific to GPUs, the errors are originating from HBM2e memory chips on the GPU.
As a first step, I'm trying to leverage the existing EDAC interfaces to report the HBM errors.
Page retirement and storing the bad pages info on a persistent storage can be the next steps.
Quoted 5 lines
What is the strategy here?
Your 0th message talks about the "what" but what gets added is not important - the "why" is.
Sure, i will update with the why.
Quoted 37 lines
$ grep -r . /sys/devices/system/edac/mc/ 2>/dev/null /sys/devices/system/edac/mc/power/runtime_active_time:0 /sys/devices/system/edac/mc/power/runtime_status:unsupported /sys/devices/system/edac/mc/power/runtime_suspended_time:0 /sys/devices/system/edac/mc/power/control:auto /sys/devices/system/edac/mc/mc0/ce_count:0 /sys/devices/system/edac/mc/mc0/rank7/dimm_ue_count:0 /sys/devices/system/edac/mc/mc0/rank7/dimm_mem_type:Unbuffered-DDR4 /sys/devices/system/edac/mc/mc0/rank7/power/runtime_active_time:0 /sys/devices/system/edac/mc/mc0/rank7/power/runtime_status:unsupported /sys/devices/system/edac/mc/mc0/rank7/power/runtime_suspended_time:0 /sys/devices/system/edac/mc/mc0/rank7/power/control:auto /sys/devices/system/edac/mc/mc0/rank7/dimm_dev_type:Unknown /sys/devices/system/edac/mc/mc0/rank7/size:8192 /sys/devices/system/edac/mc/mc0/rank7/dimm_ce_count:0 /sys/devices/system/edac/mc/mc0/rank7/dimm_label:mc#0csrow#3channel#1 /sys/devices/system/edac/mc/mc0/rank7/dimm_location:csrow 3 channel 1 /sys/devices/system/edac/mc/mc0/rank7/dimm_edac_mode:SECDED /sys/devices/system/edac/mc/mc0/topmem:0x00000000e0000000 /sys/devices/system/edac/mc/mc0/mc_name:F17h /sys/devices/system/edac/mc/mc0/rank5/dimm_ue_count:0 /sys/devices/system/edac/mc/mc0/rank5/dimm_mem_type:Unbuffered-DDR4 /sys/devices/system/edac/mc/mc0/rank5/power/runtime_active_time:0 /sys/devices/system/edac/mc/mc0/rank5/power/runtime_status:unsupported /sys/devices/system/edac/mc/mc0/rank5/power/runtime_suspended_time:0 /sys/devices/system/edac/mc/mc0/rank5/power/control:auto /sys/devices/system/edac/mc/mc0/rank5/dimm_dev_type:Unknown /sys/devices/system/edac/mc/mc0/rank5/size:8192 /sys/devices/system/edac/mc/mc0/rank5/dimm_ce_count:0 /sys/devices/system/edac/mc/mc0/rank5/dimm_label:mc#0csrow#2channel#1 /sys/devices/system/edac/mc/mc0/rank5/dimm_location:csrow 2 channel 1 /sys/devices/system/edac/mc/mc0/rank5/dimm_edac_mode:SECDED /sys/devices/system/edac/mc/mc0/dram_hole:0 0 0 /sys/devices/system/edac/mc/mc0/ce_noinfo_count:0 ...
Quoted 3 lines
--
Regards/Gruss,
Boris.
Regards,
Naveen
Borislav Petkov
maintainerRe: [PATCH v6 5/5] EDAC/amd64: Enumerate memory on Aldebaran GPU nodes
Quoted 5 lines · Naveen Krishna
The errors are not specific to GPUs, the errors are originating from HBM2e memory chips on the GPU.
As a first step, I'm trying to leverage the existing EDAC interfaces to report the HBM errors.
Report them how? How do the HBM chips fit in the EDAC sysfs hierarchy? Does it even work with the current hierarchy or does EDAC need more major restructuring?
You can send me an example from sysfs on such a system, privately is fine too.
Quoted 2 lines
Page retirement and storing the bad pages info on a persistent storage can be the next steps.
If you're thinking about plugging this into memory_failure(), then this has nothing to do with EDAC.
All EDAC can give you is error count numbers in sysfs.
So I'd like to see where this is going first, and whether it is even worth it adding it to EDAC.
Thx.
Signature · 4 lines
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette