From: Umang Chheda <umang.chheda@oss.qualcomm.com>
To: Catalin Marinas <catalin.marinas@arm.com>,
Borislav Petkov <bp@alien8.de>
Cc: Ruidong Tian <tianruidong@linux.alibaba.com>,
Will Deacon <will@kernel.org>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Hanjun Guo <guohanjun@huawei.com>,
Sudeep Holla <sudeep.holla@kernel.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>, Tony Luck <tony.luck@intel.com>,
Thomas Gleixner <tglx@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Robin Murphy <robin.murphy@arm.com>,
linux-acpi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-edac@vger.kernel.org,
zhuo.song@linux.alibaba.com, oliver.yang@linux.alibaba.com,
James Morse <james.morse@arm.com>, Rob Herring <robh@kernel.org>
Subject: Re: [PATCH v7 00/16] Support Armv8 RAS Extensions for Kernel-first error handling
Date: Mon, 20 Jul 2026 13:56:44 +0530 [thread overview]
Message-ID: <89f07e36-ac7e-4895-8d2f-5c509c6eabdb@oss.qualcomm.com> (raw)
In-Reply-To: <ak6HPmosSUleJFYU@arm.com>
Hello All/Catalin,
On 7/8/2026 10:52 PM, Catalin Marinas wrote:
> On Tue, Jul 07, 2026 at 07:41:31PM -0700, Borislav Petkov wrote:
>> 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
> [...]
>> 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.
>
> I will volunteer James Morse (he doesn't know yet) as the Arm RAS
> expert. He's away this week, hopefully can have a look when he gets
> back. For the ACPI bits, we have Lorenzo, Hanjun, Sudeep who should be
> able to review.
>
> Adding Rob Herring as well who's been giving some feedback on the DT
> counterpart:
>
> https://lore.kernel.org/all/20260505-aest-devicetree-support-v1-0-d5d6ffacf0a5@oss.qualcomm.com/
>
> I have some vague recollection James wanting to start with something
> simpler like EDAC and do DT first but I may be wrong or things could
> have changed since. So, let's wait for James to comment.
>
JYFI, I have v2 [1] of DT front-end support for ARM RAS.
https://lore.kernel.org/lkml/20260720081954.1858180-1-umang.chheda@oss.qualcomm.com/
Thanks,
Umang
prev parent reply other threads:[~2026-07-20 8:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 7:15 [PATCH v7 00/16] Support Armv8 RAS Extensions for Kernel-first error handling Ruidong Tian
2026-06-02 7:15 ` [PATCH v7 01/16] ACPI/AEST: Register arm64_ras platform devices from AEST v2 Ruidong Tian
2026-06-02 7:15 ` [PATCH v7 02/16] arm64: ras: Add probe/remove for arm64_ras driver Ruidong Tian
2026-06-02 7:15 ` [PATCH v7 03/16] arm64: ras: Unify the read/write interface for system and MMIO registers Ruidong Tian
2026-06-02 7:15 ` [PATCH v7 04/16] arm64: ras: Support RAS Common Fault Injection Model Extension Ruidong Tian
2026-06-02 7:15 ` [PATCH v7 05/16] arm64: ras: Plumb AEST interrupts as platform IRQ resources Ruidong Tian
2026-06-02 7:15 ` [PATCH v7 06/16] arm64: ras: Enable error reporting Ruidong Tian
2026-06-02 7:15 ` [PATCH v7 07/16] arm64: ras: Add error record processing and interrupt handling Ruidong Tian
2026-06-02 7:15 ` [PATCH v7 08/16] arm64: ras: Handle memory failure for uncorrectable errors Ruidong Tian
2026-06-02 7:15 ` [PATCH v7 09/16] arm64: ras: Probe RAS architecture version Ruidong Tian
2026-06-02 7:15 ` [PATCH v7 10/16] arm64: ras: Support CE threshold of error record Ruidong Tian
2026-06-02 7:15 ` [PATCH v7 11/16] arm64: ras: Add RAS decode notifier chain Ruidong Tian
2026-06-02 7:15 ` [PATCH v7 12/16] arm64: ras: Expose config abi through debugfs Ruidong Tian
2026-06-02 7:15 ` [PATCH v7 13/16] arm64: ras: Introduce ras inject interface Ruidong Tian
2026-06-02 7:15 ` [PATCH v7 14/16] arm64: ras: support vendor node CMN700 Ruidong Tian
2026-06-02 7:15 ` [PATCH v7 15/16] arm64: ras: Introduce ras error storm mitigation Ruidong Tian
2026-06-02 7:15 ` [PATCH v7 16/16] trace, ras: add ARM RAS extension trace event Ruidong Tian
2026-07-08 2:41 ` [PATCH v7 00/16] Support Armv8 RAS Extensions for Kernel-first error handling Borislav Petkov
2026-07-08 17:22 ` Catalin Marinas
2026-07-20 8:26 ` Umang Chheda [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=89f07e36-ac7e-4895-8d2f-5c509c6eabdb@oss.qualcomm.com \
--to=umang.chheda@oss.qualcomm.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=guohanjun@huawei.com \
--cc=james.morse@arm.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=oliver.yang@linux.alibaba.com \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.com \
--cc=sudeep.holla@kernel.org \
--cc=tglx@kernel.org \
--cc=tianruidong@linux.alibaba.com \
--cc=tony.luck@intel.com \
--cc=will@kernel.org \
--cc=zhuo.song@linux.alibaba.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox