Skip to contentSkip to conversation

Add L1 and L2 error detection for A72

PATCH Superseded Vijay Balakrishna 4 participants 15 messages May 16, 2025 – May 23, 2025

Subsystems (2)

v9 of 12 Superseded Latest is v12 →

lore
Share & tools
lore
#0 lore raw

v9 cover Add L1 and L2 error detection for A72

This is an attempt to revive [v5] series. I have attempted to address comments and suggestions from Marc Zyngier since [v5]. Additionally, I have limited the support only for A72 processors per [v8] discussion. Testing the driver on a problematic A72 SoC has led to the detection of Correctable Errors (CEs). Below are logs captured from the problematic SoC during various boot instances.

[  876.896022] EDAC DEVICE0: CE: cortex-arm64-edac instance: cpu2 block: L1 count: 1 'L1-D Data RAM correctable error(s) on CPU 2'
[ 3700.978086] EDAC DEVICE0: CE: cortex-arm64-edac instance: cpu2 block: L1 count: 1 'L1-D Data RAM correctable error(s) on CPU 2'
[  976.956158] EDAC DEVICE0: CE: cortex-arm64-edac instance: cpu2 block: L1 count: 1 'L1-D Data RAM correctable error(s) on CPU 2'
[ 1427.933606] EDAC DEVICE0: CE: cortex-arm64-edac instance: cpu2 block: L1 count: 1 'L1-D Data RAM correctable error(s) on CPU 2'
[  192.959911] EDAC DEVICE0: CE: cortex-arm64-edac instance: cpu2 block: L1 count: 1 'L1-D Data RAM correctable error(s) on CPU 2'

Testing our product kernel involved adding the 'edac-enabled' property to CPU nodes in the DTS. For mainline sanity checks, we tested under QEMU by extracting the default DTB and modifying the DTS to include the 'edac-enabled' property. We then verified the presence of /sysfs nodes for CE and UE counts for the emulated A72 CPUs.

Our primary focus is on A72. We have a significant number of A72-based systems in our fleet, and timely replacements via monitoring CEs will be instrumental in managing them effectively.

I am eager to hear your suggestions and feedback on this series.

Thanks,
Vijay

[v5] https://lore.kernel.org/all/[email protected]/#t
[v6] https://lore.kernel.org/all/[email protected]/
[v7] https://lore.kernel.org/all/[email protected]/#t
[v8] https://lore.kernel.org/all/[email protected]/

Changes since v8:
- removed support for A53 and A57
- added entry to MAINTAINERS
- added missing module exit point to enable unload

Changes since v7:
- v5 was based on the internal product kernel, identified following upon review
- correct format specifier to print CPUID/WAY
- removal of unused dynamic attributes for edac_device_alloc_ctl_info()
- driver remove callback return type is void

Changes since v6:
- restore the change made in [v5] to clear CPU/L2 syndrome registers back to read_errors()
- upon detecting a valid error, clear syndrome registers immediately to avoid clobbering between the read and write (Marc)
- NULL return check for of_get_cpu_node() (Tyler)
- of_node_put() to avoid refcount issue (Tyler)
- quotes are dropped in yaml file (Krzysztof)

Changes since v5:
- rebase on v6.15-rc1
- the syndrome registers for CPU/L2 memory errors are cleared only upon detecting an error and an isb() after for synchronization (Marc)
- "edac-enabled" hunk moved to initial patch to avoid breaking virtual environments (Marc)
- to ensure compatibility across all three families, we are not reporting "L1 Dirty RAM," documented only in the A53 TRM
- above prompted changing default CPU L1 error meesage from "unknown" to "Unspecified"
- capturing CPUID/WAY information in L2 memory error log (Marc)
- module license from "GPL v2" to "GPL" (checkpatch.pl warning)
- extend support for A72

Sascha Hauer (2):
drivers/edac: Add L1 and L2 error detection for A72
dt-bindings: arm: cpus: Add edac-enabled property

Vijay Balakrishna (1):
EDAC: Add EDAC driver for Cortex A72

 .../devicetree/bindings/arm/cpus.yaml         |   6 +
 MAINTAINERS                                   |   7 +
 drivers/edac/Kconfig                          |   8 +
 drivers/edac/Makefile                         |   1 +
 drivers/edac/edac_a72.c                       | 233 ++++++++++++++++++
 5 files changed, 255 insertions(+)
 create mode 100644 drivers/edac/edac_a72.c

base-commit: fee3e843b309444f48157e2188efa6818bae85cf

Signature · 1 line
2.49.0
#1 lore raw

PATCH v9 1/3 drivers/edac: Add L1 and L2 error detection for A72

From: Sascha Hauer <[email protected]>

The Cortex A72 cores have error detection capabilities for the L1/L2 Caches, this patch adds a driver for them. The selected errors to detect/report are by reading CPU/L2 memory error syndrome registers.

Unfortunately there is no robust way to inject errors into the caches, so this driver doesn't contain any code to actually test it. It has been tested though with code taken from an older version [1] of this driver. For reasons stated in thread [1], the error injection code is not suitable for mainline, so it is removed from the driver.

[1] https://lore.kernel.org/all/[email protected]/#t

---
 drivers/edac/Kconfig    |   8 ++
 drivers/edac/Makefile   |   1 +
 drivers/edac/edac_a72.c | 233 ++++++++++++++++++++++++++++++++++++++++
 3 files changed, 242 insertions(+)
 create mode 100644 drivers/edac/edac_a72.c
drivers/edac/Kconfig +8 -0
index 19ad3c3b675d..7c99bb04b0c4 100644
@@ -576,4 +576,12 @@ config EDAC_LOONGSON
 	  errors (CE) only. Loongson-3A5000/3C5000/3D5000/3A6000/3C6000
 	  are compatible.
 
+config EDAC_CORTEX_A72
+	tristate "ARM Cortex A72"
+	depends on ARM64
+	help
+	  Support for L1/L2 cache error detection for ARM Cortex A72 processor.
+	  The detected and reported erros are from reading CPU/L2 memory error
+	  syndrome registers.
+
 endif # EDAC
drivers/edac/Makefile +1 -0
index a8f2d8f6c894..835539b5d5af 100644
@@ -88,3 +88,4 @@ obj-$(CONFIG_EDAC_NPCM)			+= npcm_edac.o
 obj-$(CONFIG_EDAC_ZYNQMP)		+= zynqmp_edac.o
 obj-$(CONFIG_EDAC_VERSAL)		+= versal_edac.o
 obj-$(CONFIG_EDAC_LOONGSON)		+= loongson_edac.o
+obj-$(CONFIG_EDAC_CORTEX_A72)	+= edac_a72.o
drivers/edac/edac_a72.c new file +233 -0

233 lines not on this page · raw message

Signature · 1 line
2.49.0
maintainer
#2 lore raw

Re: [PATCH 1/3] drivers/edac: Add L1 and L2 error detection for A72

Quoted 1 line · Vijay Balakrishna

Subject: Re: [PATCH 1/3] drivers/edac: Add L1 and L2 error detection for A72

git log drivers/edac/

to get inspired about proper commit titles and prefix.

Quoted 4 lines

From: Sascha Hauer <[email protected]>

The Cortex A72 cores have error detection capabilities for the L1/L2 Caches, this patch adds a driver for them. The selected errors

Avoid having "This patch" or "This commit" in the commit message. It is tautologically useless.

Also, do

$ git grep 'This patch' Documentation/process

for more details.

Quoted 25 lines

to detect/report are by reading CPU/L2 memory error syndrome registers.

Unfortunately there is no robust way to inject errors into the caches, so this driver doesn't contain any code to actually test it. It has been tested though with code taken from an older version [1] of this driver. For reasons stated in thread [1], the error injection code is not suitable for mainline, so it is removed from the driver.

[1] https://lore.kernel.org/all/[email protected]/#t

---
 drivers/edac/Kconfig    |   8 ++
 drivers/edac/Makefile   |   1 +
 drivers/edac/edac_a72.c | 233 ++++++++++++++++++++++++++++++++++++++++
 3 files changed, 242 insertions(+)
 create mode 100644 drivers/edac/edac_a72.c
drivers/edac/Kconfig +0 -0
index 19ad3c3b675d..7c99bb04b0c4 100644

drivers/edac/Kconfig config EDAC_LOONGSON · line 584

Quoted 9 lines
drivers/edac/Kconfig +6 -0
@@ -576,4 +576,12 @@ config EDAC_LOONGSON
 	  errors (CE) only. Loongson-3A5000/3C5000/3D5000/3A6000/3C6000
 	  are compatible.
 
+config EDAC_CORTEX_A72
+	tristate "ARM Cortex A72"
+	depends on ARM64
+	help
+	  Support for L1/L2 cache error detection for ARM Cortex A72 processor.
+	  The detected and reported erros are from reading CPU/L2 memory error

+ The detected and reported erros are from reading memory error
Unknown word [erros] in Kconfig help text.
Suggestions: ['errors', 'Eros', 'errs', 'euros'...

drivers/edac/Makefile obj-$(CONFIG_EDAC_NPCM) += npcm_edac.o · line 91

Quoted 12 lines
drivers/edac/Kconfig +2 -0
+	  syndrome registers.
+
 endif # EDAC
drivers/edac/Makefile +1 -0
index a8f2d8f6c894..835539b5d5af 100644
@@ -88,3 +88,4 @@ obj-$(CONFIG_EDAC_NPCM)			+= npcm_edac.o
 obj-$(CONFIG_EDAC_ZYNQMP)		+= zynqmp_edac.o
 obj-$(CONFIG_EDAC_VERSAL)		+= versal_edac.o
 obj-$(CONFIG_EDAC_LOONGSON)		+= loongson_edac.o
+obj-$(CONFIG_EDAC_CORTEX_A72)	+= edac_a72.o

I don't know what tree you are preparing your patches against - it should be this one:

https://git.kernel.org/pub/scm/linux/kernel/git/ras/ras.git/log/?h=edac-for-next

but the indentation level here is wrong:

obj-$(CONFIG_EDAC_ZYNQMP)^I^I+= zynqmp_edac.o$ obj-$(CONFIG_EDAC_VERSAL)^I^I+= versal_edac.o$ obj-$(CONFIG_EDAC_LOONGSON)^I^I+= loongson_edac.o$ obj-$(CONFIG_EDAC_CORTEX_A72)^I+= edac_a72.o$

			     ^^^

after I apply your patch.

Quoted 37 lines
drivers/edac/edac_a72.c new file +31 -0
new file mode 100644
index 000000000000..13acd7e7cef0
@@ -0,0 +1,233 @@
+// SPDX-License-Identifier: GPL-2.0
+/*
+ * Cortex A72 EDAC L1 and L2 cache error detection
+ *
+ * Copyright (c) 2020 Pengutronix, Sascha Hauer <[email protected]>
+ *
+ * Based on Code from:
+ * Copyright (c) 2018, NXP Semiconductor
+ * Author: York Sun <[email protected]>
+ *
+ */
+
+#include <linux/module.h>
+#include <linux/of.h>
+#include <linux/bitfield.h>
+#include <asm/smp_plat.h>
+
+#include "edac_module.h"
+
+#define DRVNAME				"edac-a72"
+
+#define CPUMERRSR_EL1_RAMID		GENMASK(30, 24)
+
+#define CPUMERRSR_EL1_VALID		BIT(31)
+#define CPUMERRSR_EL1_FATAL		BIT(63)
+
+#define L1_I_TAG_RAM			0x00
+#define L1_I_DATA_RAM			0x01
+#define L1_D_TAG_RAM			0x08
+#define L1_D_DATA_RAM			0x09
+#define TLB_RAM				0x18

drivers/edac/edac_a72.c line 41

Quoted 10 lines
drivers/edac/edac_a72.c new file +10 -0
+
+#define L2MERRSR_EL1_CPUID_WAY	GENMASK(21, 18)
+
+#define L2MERRSR_EL1_VALID		BIT(31)
+#define L2MERRSR_EL1_FATAL		BIT(63)
+
+struct merrsr {
+	u64 cpumerr;
+	u64 l2merr;
+};

That struct naming needs some making the names more understandable. "merrsr" doesn't tell me anything.

drivers/edac/edac_a72.c line 46

Quoted 5 lines
drivers/edac/edac_a72.c new file +5 -0
+
+#define MESSAGE_SIZE 64
+
+#define SYS_CPUMERRSR_EL1			sys_reg(3, 1, 15, 2, 2)
+#define SYS_L2MERRSR_EL1			sys_reg(3, 1, 15, 2, 3)

Please group all defines together, align them vertically and then put other definitions below. Look at other drivers for inspiration.

drivers/edac/edac_a72.c line 55

Quoted 9 lines
drivers/edac/edac_a72.c new file +9 -0
+
+static struct cpumask compat_mask;
+
+static void report_errors(struct edac_device_ctl_info *edac_ctl, int cpu,
+			  struct merrsr *merrsr)
+{
+	char msg[MESSAGE_SIZE];
+	u64 cpumerr = merrsr->cpumerr;
+	u64 l2merr = merrsr->l2merr;

The edac-tree preferred ordering of variable declarations at the beginning of a function is reverse fir tree order::

	struct long_struct_name *descriptive_name;
	unsigned long foo, bar;
	unsigned int tmp;
	int ret;

The above is faster to parse than the reverse ordering::

	int ret;
	unsigned int tmp;
	unsigned long foo, bar;
	struct long_struct_name *descriptive_name;

And even more so than random ordering::

	unsigned long foo, bar;
	int ret;
	struct long_struct_name *descriptive_name;
	unsigned int tmp;

Please check all your functions.

Quoted 55 lines
drivers/edac/edac_a72.c new file +55 -0
+
+	if (cpumerr & CPUMERRSR_EL1_VALID) {
+		const char *str;
+		bool fatal = cpumerr & CPUMERRSR_EL1_FATAL;
+
+		switch (FIELD_GET(CPUMERRSR_EL1_RAMID, cpumerr)) {
+		case L1_I_TAG_RAM:
+			str = "L1-I Tag RAM";
+			break;
+		case L1_I_DATA_RAM:
+			str = "L1-I Data RAM";
+			break;
+		case L1_D_TAG_RAM:
+			str = "L1-D Tag RAM";
+			break;
+		case L1_D_DATA_RAM:
+			str = "L1-D Data RAM";
+			break;
+		case TLB_RAM:
+			str = "TLB RAM";
+			break;
+		default:
+			str = "Unspecified";
+			break;
+		}
+
+		snprintf(msg, MESSAGE_SIZE, "%s %s error(s) on CPU %d",
+			 str, fatal ? "fatal" : "correctable", cpu);
+
+		if (fatal)
+			edac_device_handle_ue(edac_ctl, cpu, 0, msg);
+		else
+			edac_device_handle_ce(edac_ctl, cpu, 0, msg);
+	}
+
+	if (l2merr & L2MERRSR_EL1_VALID) {
+		bool fatal = l2merr & L2MERRSR_EL1_FATAL;
+
+		snprintf(msg, MESSAGE_SIZE, "L2 %s error(s) on CPU %d CPUID/WAY 0x%lx",
+			 fatal ? "fatal" : "correctable", cpu,
+			 FIELD_GET(L2MERRSR_EL1_CPUID_WAY, l2merr));
+		if (fatal)
+			edac_device_handle_ue(edac_ctl, cpu, 1, msg);
+		else
+			edac_device_handle_ce(edac_ctl, cpu, 1, msg);
+	}
+}
+
+static void read_errors(void *data)
+{
+	struct merrsr *merrsr = data;
+
+	merrsr->cpumerr = read_sysreg_s(SYS_CPUMERRSR_EL1);
+	if (merrsr->cpumerr & CPUMERRSR_EL1_VALID) {
+		write_sysreg_s(0, SYS_CPUMERRSR_EL1);

drivers/edac/edac_a72.c line 120

Quoted 10 lines
drivers/edac/edac_a72.c new file +10 -0
+		isb();
+	}
+	merrsr->l2merr = read_sysreg_s(SYS_L2MERRSR_EL1);
+	if (merrsr->l2merr & L2MERRSR_EL1_VALID) {
+		write_sysreg_s(0, SYS_L2MERRSR_EL1);
+		isb();
+	}
+}
+
+static void cortex_arm64_edac_check(struct edac_device_ctl_info *edac_ctl)

All static functions don't need a prefix "cortex_arm64_".

drivers/edac/edac_a72.c line 123

Quoted 3 lines
drivers/edac/edac_a72.c new file +3 -0
+{
+	struct merrsr merrsr;
+	int cpu;

I'd venture a guess you need to protect here against CPU hotplug...

Quoted 59 lines
drivers/edac/edac_a72.c new file +59 -0
+	for_each_cpu_and(cpu, cpu_online_mask, &compat_mask) {
+		smp_call_function_single(cpu, read_errors, &merrsr, true);
+		report_errors(edac_ctl, cpu, &merrsr);
+	}
+}
+
+static int cortex_arm64_edac_probe(struct platform_device *pdev)
+{
+	struct edac_device_ctl_info *edac_ctl;
+	struct device *dev = &pdev->dev;
+	int rc;
+
+	edac_ctl = edac_device_alloc_ctl_info(0, "cpu",
+					      num_possible_cpus(), "L", 2, 1,
+					      edac_device_alloc_index());
+	if (!edac_ctl)
+		return -ENOMEM;
+
+	edac_ctl->edac_check = cortex_arm64_edac_check;
+	edac_ctl->dev = dev;
+	edac_ctl->mod_name = dev_name(dev);
+	edac_ctl->dev_name = dev_name(dev);
+	edac_ctl->ctl_name = DRVNAME;
+	dev_set_drvdata(dev, edac_ctl);
+
+	rc = edac_device_add_device(edac_ctl);
+	if (rc)
+		goto out_dev;
+
+	return 0;
+
+out_dev:
+	edac_device_free_ctl_info(edac_ctl);
+
+	return rc;
+}
+
+static void cortex_arm64_edac_remove(struct platform_device *pdev)
+{
+	struct edac_device_ctl_info *edac_ctl = dev_get_drvdata(&pdev->dev);
+
+	edac_device_del_device(edac_ctl->dev);
+	edac_device_free_ctl_info(edac_ctl);
+}
+
+static const struct of_device_id cortex_arm64_edac_of_match[] = {
+	{ .compatible = "arm,cortex-a72" },
+	{}
+};
+MODULE_DEVICE_TABLE(of, cortex_arm64_edac_of_match);
+
+static struct platform_driver cortex_arm64_edac_driver = {
+	.probe = cortex_arm64_edac_probe,
+	.remove = cortex_arm64_edac_remove,
+	.driver = {
+		.name = DRVNAME,
+	},
+};
+

drivers/edac/edac_a72.c line 193

Quoted 10 lines
drivers/edac/edac_a72.c new file +10 -0
+static int __init cortex_arm64_edac_driver_init(void)
+{
+	struct device_node *np;
+	int cpu;
+	struct platform_device *pdev;
+	int err;
+
+	for_each_possible_cpu(cpu) {
+		np = of_get_cpu_node(cpu, NULL);
+

^ Superfluous newline.

drivers/edac/edac_a72.c line 195

Quoted 2 lines
drivers/edac/edac_a72.c new file +2 -0
+		if (!np) {
+			pr_warn("failed to find device node for cpu %d\n", cpu);

In visible strings s/cpu/CPU/g

Quoted 10 lines
drivers/edac/edac_a72.c new file +10 -0
+			continue;
+		}
+		if (!of_match_node(cortex_arm64_edac_of_match, np))
+			continue;
+		if (!of_property_read_bool(np, "edac-enabled"))
+			continue;
+		cpumask_set_cpu(cpu, &compat_mask);
+		of_node_put(np);
+	}
+

drivers/edac/edac_a72.c line 215

Quoted 10 lines
drivers/edac/edac_a72.c new file +10 -0
+	if (cpumask_empty(&compat_mask))
+		return 0;
+
+	err = platform_driver_register(&cortex_arm64_edac_driver);
+	if (err)
+		return err;
+
+	pdev = platform_device_register_simple(DRVNAME, -1, NULL, 0);
+	if (IS_ERR(pdev)) {
+		pr_err("failed to register cortex arm64 edac device\n");

That driver is called edac_a72 now.

"cortex arm64 edac" is too broad.

Quoted 6 lines
drivers/edac/edac_a72.c new file +6 -0
+		platform_driver_unregister(&cortex_arm64_edac_driver);
+		return PTR_ERR(pdev);
+	}
+
+	return 0;
+}
Signature · 4 lines
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette
#3 lore raw

Re: [PATCH 1/3] drivers/edac: Add L1 and L2 error detection for A72

Quoted 8 lines · Borislav Petkov

I'd venture a guess you need to protect here against CPU hotplug...

drivers/edac/edac_a72.c line 130

Quoted 6 lines
drivers/edac/edac_a72.c new file +6 -0
+	for_each_cpu_and(cpu, cpu_online_mask, &compat_mask) {
+		smp_call_function_single(cpu, read_errors, &merrsr, true);
+		report_errors(edac_ctl, cpu, &merrsr);
+	}
+}
+

Hi Boris,

I appreciate you highlighting the CPU hotplug issue. Upon further review of surrounding code, I realized we must ensure that the data passed to read_errors() is per-CPU.

Thank you for your review. I will address the remainder of your comments promptly.

Vijay

#4 lore raw

Re: [PATCH 1/3] drivers/edac: Add L1 and L2 error detection for A72

Quoted 12 lines · Vijay Balakrishna
Quoted 8 lines · Borislav Petkov

I'd venture a guess you need to protect here against CPU hotplug...

Review

Quoted 6 lines

+    for_each_cpu_and(cpu, cpu_online_mask, &compat_mask) { +        smp_call_function_single(cpu, read_errors, &merrsr, true); +        report_errors(edac_ctl, cpu, &merrsr);
+    }

(quoted diff) +2 -0
+}
+

Hi Boris,

Quoted 1 line

I appreciate you highlighting the CPU hotplug issue. Upon further review of surrounding code, I realized we must ensure that the data passed to read_errors() is per-CPU.

Actually, per-CPU data not needed as we are passing true -- wait until function has completed on other CPUs.

maintainer
#5 lore raw

Re: [PATCH 1/3] drivers/edac: Add L1 and L2 error detection for A72

Quoted 13 lines · Vijay Balakrishna
Quoted 12 lines · Vijay Balakrishna
Quoted 8 lines · Borislav Petkov

I'd venture a guess you need to protect here against CPU hotplug...

Review

Quoted 6 lines

+    for_each_cpu_and(cpu, cpu_online_mask, &compat_mask) { +        smp_call_function_single(cpu, read_errors, &merrsr, true); +        report_errors(edac_ctl, cpu, &merrsr);
+    }

(quoted diff) +2 -0
+}
+

Hi Boris,

Quoted 6 lines
Quoted 3 lines

I appreciate you highlighting the CPU hotplug issue. Upon further review of surrounding code, I realized we must ensure that the data passed to read_errors() is per-CPU.

Actually, per-CPU data not needed as we are passing true -- wait until function has completed on other CPUs.

What happens if @cpu above gets offlined right before you do smp_call_function_single() ?

Signature · 4 lines
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette
#6 lore raw

Re: [PATCH 1/3] drivers/edac: Add L1 and L2 error detection for A72

Quoted 18 lines · Borislav Petkov
Quoted 17 lines · Vijay Balakrishna
Quoted 15 lines · Vijay Balakrishna
Quoted 8 lines · Borislav Petkov

I'd venture a guess you need to protect here against CPU hotplug...

Review

Quoted 6 lines

+    for_each_cpu_and(cpu, cpu_online_mask, &compat_mask) { +        smp_call_function_single(cpu, read_errors, &merrsr, true); +        report_errors(edac_ctl, cpu, &merrsr);
+    }

(quoted diff) +2 -0
+}
+

Hi Boris,

I appreciate you highlighting the CPU hotplug issue. Upon further review of surrounding code, I realized we must ensure that the data passed to read_errors() is per-CPU.

Quoted 5 lines
Quoted 2 lines

Actually, per-CPU data not needed as we are passing true -- wait until function has completed on other CPUs.

What happens if @cpu above gets offlined right before you do smp_call_function_single() ?

We can see inconsistent behavior or kernel crash/hang. You are correct, we need to protect against CPU hotplug. I will add cpus_read_lock()/cpus_read_unlock().

Thanks,
Vijay

#7 lore raw

Re: [PATCH 1/3] drivers/edac: Add L1 and L2 error detection for A72

In reply to Vijay Balakrishna
Quoted 12 lines · On Thu, 15 May 2025 17:06:11 -0700 Vijay Balakrishna…

From: Sascha Hauer <[email protected]>

The Cortex A72 cores have error detection capabilities for the L1/L2 Caches, this patch adds a driver for them. The selected errors to detect/report are by reading CPU/L2 memory error syndrome registers.

Unfortunately there is no robust way to inject errors into the caches, so this driver doesn't contain any code to actually test it. It has been tested though with code taken from an older version [1] of this driver. For reasons stated in thread [1], the error injection code is not suitable for mainline, so it is removed from the driver.

Quoted 5 lines

[1] https://lore.kernel.org/all/[email protected]/#t

Hi.

Some issues with release of device_nodes in the of parsing code.

Jonathan

Quoted 6 lines
drivers/edac/edac_a72.c new file +0 -0
new file mode 100644
index 000000000000..13acd7e7cef0

drivers/edac/edac_a72.c line 10

Quoted 10 lines
drivers/edac/edac_a72.c new file +10 -0
@@ -0,0 +1,233 @@
+// SPDX-License-Identifier: GPL-2.0
+/*
+ * Cortex A72 EDAC L1 and L2 cache error detection
+ *
+ * Copyright (c) 2020 Pengutronix, Sascha Hauer <[email protected]>
+ *
+ * Based on Code from:
+ * Copyright (c) 2018, NXP Semiconductor
+ * Author: York Sun <[email protected]>
+ *

Trivial but this blank line adds nothing useful

Quoted 4 lines
drivers/edac/edac_a72.c new file +4 -0
+ */
+
+#include <linux/module.h>
+#include <linux/of.h>

drivers/edac/edac_a72.c

Quoted 10 lines
drivers/edac/edac_a72.c new file +9 -0
+#include <linux/bitfield.h>
+#include <asm/smp_plat.h>
+
 
+
+static void cortex_arm64_edac_remove(struct platform_device *pdev)
+{
+	struct edac_device_ctl_info *edac_ctl = dev_get_drvdata(&pdev->dev);
+
+	edac_device_del_device(edac_ctl->dev);

Maybe worth thinking about about devm_ versions of the functions these are undoing though not for this patch set.

Quoted 13 lines
drivers/edac/edac_a72.c new file +13 -0
+	edac_device_free_ctl_info(edac_ctl);
+}
+
+static const struct of_device_id cortex_arm64_edac_of_match[] = {
+	{ .compatible = "arm,cortex-a72" },
+	{}
+};
+MODULE_DEVICE_TABLE(of, cortex_arm64_edac_of_match);
+
+static struct platform_driver cortex_arm64_edac_driver = {
+	.probe = cortex_arm64_edac_probe,
+	.remove = cortex_arm64_edac_remove,
+	.driver = {

drivers/edac/edac_a72.c line 189

Quoted 10 lines
drivers/edac/edac_a72.c new file +10 -0
+		.name = DRVNAME,
+	},
+};
+
+static int __init cortex_arm64_edac_driver_init(void)
+{
+	struct device_node *np;
+	int cpu;
+	struct platform_device *pdev;
+	int err;

Might as well have

	int err, cpu;

drivers/edac/edac_a72.c line 192

Quoted 3 lines
drivers/edac/edac_a72.c new file +3 -0
+
+	for_each_possible_cpu(cpu) {
+		np = of_get_cpu_node(cpu, NULL);
		np = of_cpu_device_node_get(cpu);

is probably appropriate here. See docs for of_get_cpu_node - that is only meant for initial setup of the device_node to cpu logical id mapping. It uses an extra walk in the wrong direction.

drivers/edac/edac_a72.c line 199

Quoted 7 lines
drivers/edac/edac_a72.c new file +7 -0
+
+		if (!np) {
+			pr_warn("failed to find device node for cpu %d\n", cpu);
+			continue;
+		}
+		if (!of_match_node(cortex_arm64_edac_of_match, np))
+			continue;

You are holding the reference to the node which should have been released. If Borislav doesn't mind them in edac, use __free magic to handle this.

		struct device_node *np __free(device_node) = 
			of_cpu_device_node_get(cpu);

and don't manually release the node at all. It will be released on scope exit (so each iteration of the loop). This is safe for !np test as well.

Quoted 17 lines
drivers/edac/edac_a72.c new file +17 -0
+		if (!of_property_read_bool(np, "edac-enabled"))
+			continue;
+		cpumask_set_cpu(cpu, &compat_mask);
+		of_node_put(np);
+	}
+
+	if (cpumask_empty(&compat_mask))
+		return 0;
+
+	err = platform_driver_register(&cortex_arm64_edac_driver);
+	if (err)
+		return err;
+
+	pdev = platform_device_register_simple(DRVNAME, -1, NULL, 0);
+	if (IS_ERR(pdev)) {
+		pr_err("failed to register cortex arm64 edac device\n");
+		platform_driver_unregister(&cortex_arm64_edac_driver);

drivers/edac/edac_a72.c line 225

Quoted 10 lines
drivers/edac/edac_a72.c new file +9 -0
+		return PTR_ERR(pdev);
+	}
+
+	return 0;
+}
+
 
+static void __exit cortex_arm64_edac_driver_exit(void)
+{
+		platform_driver_unregister(&cortex_arm64_edac_driver);

Looks like a bonus tab.

Quoted 8 lines
drivers/edac/edac_a72.c new file +8 -0
+}
+
+module_init(cortex_arm64_edac_driver_init);
+module_exit(cortex_arm64_edac_driver_exit);
+
+MODULE_LICENSE("GPL");
+MODULE_AUTHOR("Sascha Hauer <[email protected]>");
+MODULE_DESCRIPTION("Cortex A72 L1 and L2 cache EDAC driver");
#8 lore raw

Re: [PATCH 1/3] drivers/edac: Add L1 and L2 error detection for A72

Quoted 15 lines · Jonathan Cameron
Quoted 12 lines · On Thu, 15 May 2025 17:06:11 -0700 Vijay…

From: Sascha Hauer<[email protected]>

The Cortex A72 cores have error detection capabilities for the L1/L2 Caches, this patch adds a driver for them. The selected errors to detect/report are by reading CPU/L2 memory error syndrome registers.

Unfortunately there is no robust way to inject errors into the caches, so this driver doesn't contain any code to actually test it. It has been tested though with code taken from an older version [1] of this driver. For reasons stated in thread [1], the error injection code is not suitable for mainline, so it is removed from the driver.

Quoted 8 lines
Quoted 5 lines

[1]https://lore.kernel.org/all/[email protected]/#t

Hi.

Some issues with release of device_nodes in the of parsing code.

Thank you, Jonathan for review. I'm addressing your comments and posting next series soon.

Vijay

#9 lore raw

PATCH v9 2/3 dt-bindings: arm: cpus: Add edac-enabled property

In reply to Vijay Balakrishna

From: Sascha Hauer <[email protected]>

Some ARM Cortex CPUs including A72 have Error Detection And Correction (EDAC) support on their L1 and L2 caches. This is implemented in implementation defined registers, so usage of this functionality is not safe in virtualized environments or when EL3 already uses these registers. This patch adds a edac-enabled flag which can be explicitly set when EDAC can be used.

[vijayb: Limit A72 in the commit message]
---
 Documentation/devicetree/bindings/arm/cpus.yaml | 6 ++++++
 1 file changed, 6 insertions(+)
Documentation/devicetree/bindings/arm/cpus.yaml +6 -0
index 2e666b2a4dcd..d1dc0a843d07 100644
@@ -331,6 +331,12 @@ properties:
       corresponding to the index of an SCMI performance domain provider, must be
       "perf".
 
+  edac-enabled:
+    $ref: /schemas/types.yaml#/definitions/flag
+    description:
+      Some CPUs support Error Detection And Correction (EDAC) on their L1 and
+      L2 caches. This flag marks this function as usable.
+
   qcom,saw:
     $ref: /schemas/types.yaml#/definitions/phandle
     description: |
Signature · 1 line
2.49.0
maintainer
#10 lore raw

Re: [PATCH 2/3] dt-bindings: arm: cpus: Add edac-enabled property

Quoted 9 lines · Vijay Balakrishna

From: Sascha Hauer <[email protected]>

Some ARM Cortex CPUs including A72 have Error Detection And Correction (EDAC) support on their L1 and L2 caches. This is implemented in implementation defined registers, so usage of this functionality is not safe in virtualized environments or when EL3 already uses these registers. This patch adds a edac-enabled flag which can be explicitly set when EDAC can be used.

Quoted 6 lines
[vijayb: Limit A72 in the commit message]
---
 Documentation/devicetree/bindings/arm/cpus.yaml | 6 ++++++
 1 file changed, 6 insertions(+)

This needs an Ack from DT maintainers.

Signature · 4 lines
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette
maintainer
#11 lore raw

Re: [PATCH 2/3] dt-bindings: arm: cpus: Add edac-enabled property

Quoted 11 lines · Borislav Petkov
Quoted 9 lines · Vijay Balakrishna

From: Sascha Hauer <[email protected]>

Some ARM Cortex CPUs including A72 have Error Detection And Correction (EDAC) support on their L1 and L2 caches. This is implemented in implementation defined registers, so usage of this functionality is not safe in virtualized environments or when EL3 already uses these registers. This patch adds a edac-enabled flag which can be explicitly set when EDAC can be used.

Quoted 8 lines
Quoted 6 lines
[vijayb: Limit A72 in the commit message]
---
 Documentation/devicetree/bindings/arm/cpus.yaml | 6 ++++++
 1 file changed, 6 insertions(+)

This needs an Ack from DT maintainers.

That will happen when my review comments are implemented. Those were on v1. Not this v1, but the prior v1. Version your patches correctly please.

Rob

#12 lore raw

Re: [PATCH 2/3] dt-bindings: arm: cpus: Add edac-enabled property

Quoted 19 lines · Rob Herring
Quoted 18 lines · Borislav Petkov
Quoted 15 lines · Vijay Balakrishna

From: Sascha Hauer <[email protected]>

Some ARM Cortex CPUs including A72 have Error Detection And Correction (EDAC) support on their L1 and L2 caches. This is implemented in implementation defined registers, so usage of this functionality is not safe in virtualized environments or when EL3 already uses these registers. This patch adds a edac-enabled flag which can be explicitly set when EDAC can be used.

[vijayb: Limit A72 in the commit message]
---
  Documentation/devicetree/bindings/arm/cpus.yaml | 6 ++++++
  1 file changed, 6 insertions(+)
Quoted 5 lines
Quoted 1 line

This needs an Ack from DT maintainers.

That will happen when my review comments are implemented. Those were on v1. Not this v1, but the prior v1. Version your patches correctly please.

Sorry, I will include in my next patch series.

Vijay

#13 lore raw

PATCH v9 3/3 EDAC: Add EDAC driver for Cortex A72

In reply to Vijay Balakrishna

The driver is designed to support error detection and reporting for Cortex A72 cores, specifically within their L1 and L2 cache systems.

---
 MAINTAINERS | 7 +++++++
 1 file changed, 7 insertions(+)
MAINTAINERS +7 -0
index 3563492e4eba..1fa51e39e266 100644
@@ -8430,6 +8430,13 @@ F:	Documentation/driver-api/edac.rst
 F:	drivers/edac/
 F:	include/linux/edac.h
 
+EDAC-A72
+M:	Vijay Balakrishna <[email protected]>
+M:	Tyler Hicks <[email protected]>
+L:	[email protected]
+S:	Supported
+F:	drivers/edac/edac_a72.c
+
 EDAC-DMC520
 M:	Lei Wang <[email protected]>
 L:	[email protected]
Signature · 1 line
2.49.0
maintainer
#14 lore raw

Re: [PATCH 3/3] EDAC: Add EDAC driver for Cortex A72

Quoted 17 lines · Vijay Balakrishna

The driver is designed to support error detection and reporting for Cortex A72 cores, specifically within their L1 and L2 cache systems.

---
 MAINTAINERS | 7 +++++++
 1 file changed, 7 insertions(+)
MAINTAINERS +0 -0
index 3563492e4eba..1fa51e39e266 100644
@@ -8430,6 +8430,13 @@ F:	Documentation/driver-api/edac.rst
 F:	drivers/edac/
 F:	include/linux/edac.h
 

MAINTAINERS F: Documentation/driver-api/edac.rst · line 8442

Quoted 10 lines
MAINTAINERS +7 -0
+EDAC-A72
+M:	Vijay Balakrishna <[email protected]>
+M:	Tyler Hicks <[email protected]>
+L:	[email protected]
+S:	Supported
+F:	drivers/edac/edac_a72.c
+
 EDAC-DMC520
 M:	Lei Wang <[email protected]>
 L:	[email protected]

You can merge this one with patch 1.

Signature · 4 lines
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette