[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20251130112144.GAaSwoyJuNCwJiVC1W@fat_crate.local>
Date: Sun, 30 Nov 2025 12:21:44 +0100
From: Borislav Petkov <bp@...en8.de>
To: Devang Vyas <devangnayanbhai.vyas@....com>
Cc: yazen.ghannam@....com, tony.luck@...el.com, linux-edac@...r.kernel.org,
linux-kernel@...r.kernel.org,
Ramesh Garidapuri <ramesh.garidapuri@....com>
Subject: Re: [PATCH v2] EDAC/amd64: Add support for family 19h, models 40h-4fh
On Sun, Nov 30, 2025 at 03:51:11PM +0530, Devang Vyas wrote:
> Enable AMD EDAC driver for AMD SoC family 19h with
> models 40h-4fh to support Ryzen 6000 CPUs/APUs
> ("Rembrandt"), which provides kernel-level
> infrastructure needed for RAS (Reliability, Availability
> and Serviceability) features.
>
> Added changes enhance the ability to detect and
> report memory errors on systems that utilize AMD SoCs
> from the specified family. There are 4 memory controllers
> supported by Rembrandt which enables proper error reporting
> and RAS testing on specified AMD SoCs.
>
> AMD EDAC linux driver interfaces directly with the hardware-
> error reporting mechanism present in AMD platform, otherwise
> these errors would not be surfaced through the standard Linux
> EDAC framework and RAS validation workflows would be
> incomplete.
Nope, this is reads like AI slop and too generic.
Lemme try again: we do not enable amd64_edac on client hw - only server. Why
does *this* *client* deserve an exception?
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists