Re: [PATCH v7 00/16] Support Armv8 RAS Extensions for Kernel-first error handling

From: Borislav Petkov

Date: Tue Jul 07 2026 - 22:42:18 EST


Just some superficial notes on this before we delve deep...

On Tue, Jun 02, 2026 at 03:15:23PM +0800, Ruidong Tian wrote:
> Documentation/ABI/testing/debugfs-arm64-ras | 87 ++
> MAINTAINERS | 11 +
> arch/arm64/include/asm/ras.h | 99 ++
> drivers/acpi/arm64/Kconfig | 10 +
> drivers/acpi/arm64/Makefile | 1 +
> drivers/acpi/arm64/aest.c | 423 ++++++++
> drivers/ras/Kconfig | 1 +
> drivers/ras/Makefile | 1 +
> drivers/ras/arm64/Kconfig | 16 +
> drivers/ras/arm64/Makefile | 9 +
> drivers/ras/arm64/ras-cmn.c | 479 +++++++++
> drivers/ras/arm64/ras-core.c | 1026 +++++++++++++++++++
> drivers/ras/arm64/ras-inject.c | 130 +++
> drivers/ras/arm64/ras-storm.c | 198 ++++
> drivers/ras/arm64/ras-sysfs.c | 319 ++++++
> drivers/ras/arm64/ras.h | 374 +++++++
> drivers/ras/debugfs.c | 3 +-
> drivers/ras/ras.c | 3 +
> include/linux/acpi_aest.h | 36 +
> include/linux/cpuhotplug.h | 1 +
> include/linux/ras.h | 10 +
> include/ras/ras_event.h | 79 ++
> 22 files changed, 3315 insertions(+), 1 deletion(-)
> create mode 100644 Documentation/ABI/testing/debugfs-arm64-ras
> create mode 100644 arch/arm64/include/asm/ras.h
> create mode 100644 drivers/acpi/arm64/aest.c
> create mode 100644 drivers/ras/arm64/Kconfig
> create mode 100644 drivers/ras/arm64/Makefile
> create mode 100644 drivers/ras/arm64/ras-cmn.c
> create mode 100644 drivers/ras/arm64/ras-core.c
> create mode 100644 drivers/ras/arm64/ras-inject.c
> create mode 100644 drivers/ras/arm64/ras-storm.c
> create mode 100644 drivers/ras/arm64/ras-sysfs.c

People have got to start naming their files properly. I see this everywhere in
the tree: there's "ras" in your path and then you add a "ras-" before each .c
file name.

Do not do that.

But this is not that important - what's more important is exporting generic
interfaces which are ARM64-specific. Like in patch 11. That can't work.

But that's still not that important - what is even more important is who from
ARM is going to review and maintain this? I can take a look at the generic
bits so that the RAS stuff coexists fine in drivers/ras/ but I'd need an ARM
person to take care of this.

There are enough on Cc so let's see if anyone moves.

Thx.

--
Regards/Gruss,
Boris.

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